Help Center> Cloud Search Service> Troubleshooting> Clusters> Why Do I Fail to Access CSS Using TransportClient?

Updated on 2023-10-10 GMT+08:00

View PDF

Why Do I Fail to Access CSS Using TransportClient?

Symptom

CSS cannot be accessed using the Spring Data Elasticsearch method, and the error message "None of the configured nodes are available" is displayed.

Possible Causes

Generally, cluster.name needs to be configured when you access a cluster using TransportClient. The possible cause of access failure is that the Settings.EMPTY option is used or the setting is incorrect.

Procedure

For details about how to connect a client to a cluster, see Accessing the Cluster Through the Transport Client.

Parent topic: Clusters

Previous topic: How Can I Improve Filebeat Performance?

Next topic: How Do I Handle the Error "Connection reset by peer" That Occurs When Spring Boot Uses Elasticsearch?

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot