[
https://issues.apache.org/jira/browse/SOLR-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13949515#comment-13949515
]
Hoss Man commented on SOLR-5823:
--------------------------------
Over in SOLR-5919, shalin & miller reminded me why of some really silly-stupid
stuff i forgot about the cluster & the overseer that makes my "IsOverseerTest"
broken by design. namely: collections can be sharded across a cluster w/o any
one replica of that collection being hosted on the node that is acting as
overseer.
This means two things:
1) my previous patch (prior to introducing IsOverseerTest) is still fine
2) my main usecase for why i wanted to add this method is a flawed design, and
this method won't actually help me (i don't think).
So with that in mind, i'm going to drop this issue -- if other folks see any
value to adding this method, we still can - otherwise i'll probably resolve as
"not a problem"
> 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, 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
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
