[ 
https://issues.apache.org/jira/browse/SOLR-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hoss Man updated SOLR-5823:
---------------------------

    Attachment: SOLR-5823.patch

Updated patch - removes the "name" method Tim had added, and switches the 
"ZkController.isOverseer()" method to be based on new "isAlive()" method i 
added to Overseer.java. (set to true in start(), false in close())

I beefed up Tim's test changes (noticing SOLR-5832 in the process, but that 
doesn't seem to be related to this patch) to spin up a second node "alt" and 
verify that "alt" doesn't also think it's the overseer -- so far so good.  
However when i tried to use the "ZkController.forceOverSeer()" method in the 
test code to trigger a overseer change and verify that the booleans changed, he 
test fails -- both nodes think they are the overseer.

I'm a little out of my depth here, but from what i can tell looking at how the 
overseer election is setup, i think forceOverSeer() may be fundamentally broken?

Would appreciate another set of eyes to help me sanity check this.

> Add utility function for internal code to know if it is currently the overseer
> ------------------------------------------------------------------------------
>
>                 Key: SOLR-5823
>                 URL: https://issues.apache.org/jira/browse/SOLR-5823
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Hoss Man
>         Attachments: 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
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to