I have an idea of how to implement myself, I just don't have the bandwidth to support it. :) I pretty much am the sole developer/architect/admin for our search project, so I am always hesitant to add another moving part. Will continue to poll for now.
-- Ivan On Thu, Jul 10, 2014 at 10:23 AM, [email protected] < [email protected]> wrote: > For this, an async client implementation is needed that does not close > connection after receiving a response, but waits continuously for a > response stream (events), like I tried in the websocket transport plugin > https://github.com/jprante/elasticsearch-transport-websocket > > It would be possible to attach a server-side service with > ClusterStateListener to such a websocket channel for subscribing to cluster > state events. Maybe I find time to implement this for demonstration. > > Jörg > > > On Thu, Jul 10, 2014 at 7:03 PM, Ivan Brusic <[email protected]> wrote: > >> That's what I discovered as well. I would love a client-side non-polling >> mechanism. Even tried creating a local non-data/non-master node, but it >> was not good enough. One day I will implement it as a plugin to ping an >> external monitoring API, but that would be an overkill. >> >> Cheers, >> >> Ivan >> >> >> On Thu, Jul 10, 2014 at 9:55 AM, [email protected] < >> [email protected]> wrote: >> >>> On the client side, you can't use cluster state listener, it is for >>> nodes that have access to a local copy of the master cluster state. Clients >>> must execute an action to ask for cluster state, and with the current >>> transport request/response cycle, they must poll for new events ... >>> >>> Jörg >>> >>> >>> On Thu, Jul 10, 2014 at 6:38 PM, Ivan Brusic <[email protected]> wrote: >>> >>>> Jörg, have you actually implemented your own ClusterStateListener? I >>>> never had much success. Tried using that interface or >>>> even PublishClusterStateAction.NewClusterStateListener, but either I could >>>> not configure successfully the module (the former) or received no events >>>> (the latter). Implemented on the client side, not as a plugin. >>>> >>>> Cheers, >>>> >>>> Ivan >>>> >>>> >>>> On Wed, Jul 9, 2014 at 4:21 PM, [email protected] < >>>> [email protected]> wrote: >>>> >>>>> >>>>> 4. Yes. Use org.elasticsearch.cluster.ClusterStateListener >>>>> >>>>> -- >>>> 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%3DcQBB%3DW_qG9E7i-sEc6HZeMskxKgbqzaKgqzSQ26sjgT5%2BQ%40mail.gmail.com >>>> <https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQBB%3DW_qG9E7i-sEc6HZeMskxKgbqzaKgqzSQ26sjgT5%2BQ%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/CAKdsXoE%3DyhNyt8c8fGmqauUu7KfME3jqf__vo0gGh_53gkXjKA%40mail.gmail.com >>> <https://groups.google.com/d/msgid/elasticsearch/CAKdsXoE%3DyhNyt8c8fGmqauUu7KfME3jqf__vo0gGh_53gkXjKA%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%3DcQDRdVYWfRnTrKtiZr%3DjvZU1CSzb06ijw-rFXntS%3Dg5Q1A%40mail.gmail.com >> <https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQDRdVYWfRnTrKtiZr%3DjvZU1CSzb06ijw-rFXntS%3Dg5Q1A%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/CAKdsXoHrkDe9%2BSuH3mLhTJYoPxvRBB8VY5nxPbsxsmc9S2Qr6g%40mail.gmail.com > <https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHrkDe9%2BSuH3mLhTJYoPxvRBB8VY5nxPbsxsmc9S2Qr6g%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%3DcQBrJS%3DDg0jP_AOw21m-wP6qiTZfTAdTTDJ6%3DzP362_0Fg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
