[
https://issues.apache.org/jira/browse/SOLR-15672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479714#comment-17479714
]
David Smiley commented on SOLR-15672:
-------------------------------------
The duplication is what bothers me the most. I'd feel slightly better if
someone (you? Yonik?) bothered to add javadocs on Slice.getLeader to indicate
that it's very eventual-consistent info, and that callers ideally should go to
some other place for the most up-to-date info. Additionally, this is, I
suppose, also redundant with the leader_elect place. I wonder what Curator
would do; does it make getting the current leader fast – which I think was your
objective in giving this its own fixed node. Another redundant location
(lacking docs likewise) within the code is CloudDescriptor.isLeader.
{_}Sigh{_}.
> Leader Election is flawed.
> ---------------------------
>
> Key: SOLR-15672
> URL: https://issues.apache.org/jira/browse/SOLR-15672
> Project: Solr
> Issue Type: Bug
> Reporter: Mark Robert Miller
> Priority: Major
>
> Filing this not as a work item I’m assigning my to myself, but to note a open
> issue where some notes can accumulate.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
