As mentioned by Jörg early on in the thread: "On the client side, you can't use cluster state listener"
I never bothered with a plugin version since the interaction would be too kludgy. -- Ivan On Fri, Aug 22, 2014 at 1:08 AM, 'Sandeep Ramesh Khanzode' via elasticsearch <[email protected]> wrote: > Hi Jorg, > > Can you please give a server-side or client-side example of using > CLusterStateListener? > Do I have to use a plugin. if so, which module do I register/override? > If not, do I have to use a Node Client (not a TransportClient), and > retrieve the ClusterService somehow and then register? > > Thanks > Sandeep > > > On Thursday, 10 July 2014 22:25:51 UTC+5:30, Jörg Prante 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/35f6b64e-3787-4891-a3a8-518dfd7638e3%40googlegroups.com > <https://groups.google.com/d/msgid/elasticsearch/35f6b64e-3787-4891-a3a8-518dfd7638e3%40googlegroups.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%3DcQDo1uqMJPjqcx7T4DKiCERHVthEqWEVpwW6jUcKn5x_3w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
