I am looking to transition a piece of my search infrastructure from polling the cluster's health status to hopefully receiving notifications whenever an event occurs. Using the TransportService, I registered various relevant listeners, but none of them are triggered.
Here is the gist of the code: https://gist.github.com/brusic/2dcced28e0ed753b6632 Most of it I stole^H^H^H^H^Hborrowed from ZenDiscovery. I am assuming something is not quite right with the TransportService. I tried using both a node client and a master-less/data-less client. I also suspect that the DiscoveryNodesProvider might not have been initialized correctly, but I am primarily after the events from NodesFaultDetection, which does not use the DiscoveryNodesProvider. I know I am missing something obvious, but I cannot quite spot it. Is there perhaps a different route using the TransportClient? Cheers, Ivan -- 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/CALY%3DcQC5twFLr%2By_oqkV3_SjS9T_kikG9Z%2BBi6DJ_jOydHYBCA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
