[
https://issues.apache.org/jira/browse/SOLR-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-2752:
------------------------------
Attachment: SOLR-2752.patch
Another new patch:
I moved SolrZooKeeper to the org.apache.zookeeper package so that I could add a
simulated timeout method for tests.
I also wrote a new test that starts up a bunch of replicas and then times out
the leader. After waiting for the leader to reconnect, all of the other
replicas are killed and I check that the first leader is again the leader. I
wrote this test because I knew it would fail and that on reconnecting, clients
don't jump back into the leader election process.
So I also added to the client reconnection impl - on reconnect, all SolrCores
are re-registered. This also has the advantage that any SolrCores that where
created while the connection was down are put into play. That allows the new
test to pass.
> leader-per-shard
> ----------------
>
> Key: SOLR-2752
> URL: https://issues.apache.org/jira/browse/SOLR-2752
> Project: Solr
> Issue Type: Sub-task
> Components: SolrCloud
> Reporter: Yonik Seeley
> Assignee: Mark Miller
> Fix For: 4.0
>
> Attachments: SOLR-2752.patch, SOLR-2752.patch, SOLR-2752.patch
>
>
> We need to add metadata into zookeeper about who is the leader for each
> shard, and have some kind of leader election.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
