Can a New Cluster Use the IP Address of the Old Cluster?
No.
If the IP address of a cluster changes, the possible causes are as follows:
- The private IP address of the cluster changes.
Check whether the cluster is scaled out or scaled in. The scale-out operation increases the number of private IP addresses of the cluster. The scale-in operation reduces the number of private IP addresses of the cluster. If there are services running on a node to be deleted, a fault occurs.
- The public IP address of the cluster changes.
Check whether the cluster has enabled the security mode. When creating an Elasticsearch cluster earlier than version 6.5.4, you can enable the security mode and public network access. When creating an Elasticsearch cluster of version 6.5.4 or later, you can enable the security mode. After the security mode is enabled, a public IP address is added to the cluster. To unbind a public IP address that has been bound, click Disassociate on the right of Public IP Address in the Cluster Information page of the cluster.
- The local IP address on the user side changes.
For a cluster for which public network access has been configured, you can click Set on the right of Access Control in the Basic Information area of the cluster to set the access control switch and access whitelist. Only IP addresses in the whitelist can access the cluster.
Cluster Access/Cluster Connection FAQs
- Can I Build a Kibana or Cerebro to Access CSS Clusters?
- Do Ports 9200 and 9300 Both Open?
- How Do I Use a NAT Gateway to Access CSS from the Internet?
- Can a New Cluster Use the IP Address of the Old Cluster?
- Can I Use x-pack-sql-jdbc to Access CSS Clusters and Query Data?
- Why Does My ECS Fail to Connect to a Cluster?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore
