Why Do I Fail to Access CSS Using TransportClient?
Issue
CSS cannot be accessed using the Spring Data Elasticsearch method, and the error message "None of the configured nodes are available" is displayed.
Symptom
CSS cannot be accessed using the Spring Data Elasticsearch method, and an error message is reported.
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 on how to access clusters using a client.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.