First thanks for replying. I'm working in a distributed environment and some services will use the elasticsearch service. So a kind of database is available to locate the different needed services like elasticsearch.
I work on different network so the multicast can't be used. Can the unicast ping discovery provide a discovery in this kind of organization? If not the idea is to replace the ping discovery by accessing my database to get the needed information for the discovery and detect the failure on the different nodes (The database is in charge of the heartbeat of the services and their timeout). In this case the "publish" step is not mandatory for me and will decrease the cmmunication between nodes, which is the goal of this kind of discovery. But I'm afraid that it will have a consequence on the behavior of elasticsearch. To conclude and summarize, to do that kind of discovery, I need to "register" the discovered nodes in the "DiscoveryNodes" class and update the "ClusterState". Is it exact? Another little question (I didn't read yet the documentation you provide) but if I must implement a kind of thread, do I need to make my class inherit from the "AbstractLifeCycleComponent" or can I just use an implementation of the "Runnable" interface of Java? Thanks for help. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/3dfa3a44-cca8-40b6-8a90-920ca609e470%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
