lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] [Updated] (SOLR-5823) Add utility function for internal code to know if it is currently the overseer
Date Thu, 27 Mar 2014 01:54:16 GMT


Hoss Man updated SOLR-5823:

    Attachment: SOLR-5823.patch

I tried testing this in conjunction with SOLR-5795 and ran into all sorts of problems, which
lead me to discover SOLR-5919: when using AbstractFullDistribZkTestBase, the controlClient
acts as the overseer, and none of the regular nodes in the (test) cluster do (evne though
neither the control server nor the cluster nodes seem to think the control server is part
of the cluster ... i don't understand it)

here's an updated patch that includes an "IsOverseerTest" subclassing AbstractFullDistribZkTestBase
and demonstrating the problem with the test framework in SOLR-5919 ... this depends on a change
to SystemInfoHandler to surface the "isOverseer()" info so lcinets can ask about it -- something
i'm not sure if we really want, but it was the only way i could figure out to write a test
that demonstrated this aspect of the problem.

> Add utility function for internal code to know if it is currently the overseer
> ------------------------------------------------------------------------------
>                 Key: SOLR-5823
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Hoss Man
>         Attachments: SOLR-5823.patch, SOLR-5823.patch, SOLR-5823.patch, SOLR-5823.patch,
SOLR-5823.patch, SOLR-5823.patch
> It would be useful if there was some Overseer equivalent to CloudDescriptor.isLeader()
that plugins running in solr could use to know "At this moment, am i the leader?" 

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message