Why Do I Fail to Access CSS Using TransportClient?
Issue
Accessing CSS fails using the spring data elasticsearch mode and an error message "None of the configured nodes are available" is reported.
Symptom
Accessing CSS fails using the spring data elasticsearch mode and an error message is reported.
Possible Causes
Generally, cluster.name needs to be configured when you access clusters 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, see Accessing a Cluster > Accessing a Cluster Using the Java API in Security Mode with Elasticsearch.
Last Article: Filebeat Configuration Optimization
Next Article: What Should I Do When a Cluster Is Unavailable?
Did this article solve your problem?
Thank you for your score!Your feedback would help us improve the website.