Hi,
We have been using ES 6.8 (running on VM on Azure) for some time. Since ES as a Service is available on Azure, we decided to try it out. We use Spring-ElasticSearch framework to connect to the ES instance. The Previous configuration used to set with these properties:
elasticsearch.port = 9200
elasticsearch.username=
elasticsearch.password=
spring.data.elasticsearch.cluster-name=eml
spring.data.elasticsearch.cluster-nodes=ip-address:9300
elasticsearch.host = ip-address
elasticsearch.clustername = eml
I changed it to the following after setting up an instance as service:
elasticsearch.port = 9243
elasticsearch.username=elastic
elasticsearch.password=myPassword
spring.data.elasticsearch.cluster-name = 18530cecb11645779c62ac9df64937d2
spring.data.elasticsearch.cluster-nodes:9243=18530cecb11645779c62ac9df64937d2.eastus2.azure.elastic-cloud.com
elasticsearch.host = 18530cecb11645779c62ac9df64937d2.eastus2.azure.elastic-cloud.com
elasticsearch.clustername = 18530cecb11645779c62ac9df64937d2
However, I get the following error when I start the service:
"failed to load elasticsearch nodes : org.elasticsearch.client.transport.NoNodeAvailableException: None of the configured nodes are available: [{#transport#-1}{uYK45RfYSpWJ9iMu6MTx-Q}{18530cecb11645779c62ac9df64937d2.eastus2.azure.elastic-cloud.com}{20.190.254.196:9243}]"
Is something wrong with my configuration? Though, I was able to connect to the ES and Kibana without any problem.