NodesFaultDetection is what I am looking into using, but on the client side, not as a plugin. I use similar code to create an AnalysisService locally, but no luck when it comes to TransportService actions.
-- Ivan On Wed, Apr 30, 2014 at 8:56 AM, [email protected] < [email protected]> wrote: > Not sure what events you are after, but I guess you just want to push > notifications about node failures? > > You could write a plugin that simply registers a listener to Zen's > NodesFaultDetection.addListener() and trigger the action you want (send > email, whatever) in the onNodeFailure() method of the listener. > > Jörg > > > > On Wed, Apr 30, 2014 at 5:39 PM, Ivan Brusic <[email protected]> wrote: > >> I should add that I am still on version 0.90.2. Looking to finally >> transition to 1.1 relatively soon. Our search infrastructure has had 100% >> uptime in the past two years, but it comes at the expense of not upgrading >> often. >> >> -- >> Ivan >> >> >> On Wed, Apr 30, 2014 at 6:56 AM, Ivan Brusic <[email protected]> wrote: >> >>> Would the DiscoverService solve my initial problem or only get around >>> constructing a DiscoveryNodesProvider? DiscoverService only uses >>> the InitialStateDiscoveryListener, which doesn't publish interesting events. >>> >>> I won't be near a computer in the next few days to test. >>> >>> -- >>> Ivan >>> >>> >>> On Wed, Apr 30, 2014 at 4:40 AM, [email protected] < >>> [email protected]> wrote: >>> >>>> Have you looked at InternalNode.java? >>>> >>>> Form my understanding you could try to implement your own >>>> DiscoveryModule with DiscoveryService and start it like this >>>> >>>> DiscoveryService discoService = >>>> injector.getInstance(DiscoveryService.class).start(); >>>> >>>> Jörg >>>> >>>> >>>> >>>> On Wed, Apr 30, 2014 at 12:17 AM, Ivan Brusic <[email protected]> wrote: >>>> >>>>> 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<https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQC5twFLr%2By_oqkV3_SjS9T_kikG9Z%2BBi6DJ_jOydHYBCA%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> -- >>>> 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/CAKdsXoEVGCvFFaeJmxba-UZEuKS7EK5FakqBbSgy4qUGuywtYg%40mail.gmail.com<https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEVGCvFFaeJmxba-UZEuKS7EK5FakqBbSgy4qUGuywtYg%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >> -- >> 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%3DcQBXfkD6B%3DK4fRRtdUNa3QLEj2a10J2xexZ2uuq0BR4y%3Dw%40mail.gmail.com<https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQBXfkD6B%3DK4fRRtdUNa3QLEj2a10J2xexZ2uuq0BR4y%3Dw%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- > 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/CAKdsXoGH5ifNAuK%3DvZaKEi3FnAX921pX69gy7bCwYdgiBhTv4w%40mail.gmail.com<https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGH5ifNAuK%3DvZaKEi3FnAX921pX69gy7bCwYdgiBhTv4w%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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%3DcQD-dmivL74YbFVgusgFKzbpt0i%3DFRP_0vLiWh97JOOhJw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
