[
https://issues.apache.org/jira/browse/SOLR-5243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13769807#comment-13769807
]
Yonik Seeley commented on SOLR-5243:
------------------------------------
Steps to reproduce:
{code}
#Bring up 2 nodes....
cp -rp example example2
cd example
java -Dbootstrap_confdir=./solr/collection1/conf -Dcollection.configName=myConf
-DzkRun -DnumShards=2 -jar start.jar
cd example2
java -Djetty.port=7574 -DzkHost=localhost:9983 -jar start.jar
#if both leaders aren't on port 8983, kill example2 and then bring it back up.
#look up the core name for the c2/s1 leader and unload it
curl "http://localhost:8983/solr/admin/cores?action=UNLOAD&core=c2_s1_replica2";
# now see two things:
# 1) c2/s1 is now leaderless
# 2) The leader of c3/s1 has switched to port 7574
# from the logs on port 7574 we can see that leader election was kicked off for
the wrong collection...
102432 [main-EventThread] INFO
org.apache.solr.cloud.ShardLeaderElectionContext – Running the leader process
for shard s1
102484 [main-EventThread] INFO
org.apache.solr.cloud.ShardLeaderElectionContext – Checking if I should try
and be the leader.
102484 [main-EventThread] INFO
org.apache.solr.cloud.ShardLeaderElectionContext – My last published State was
Active, it's okay to be the leader.
102484 [main-EventThread] INFO
org.apache.solr.cloud.ShardLeaderElectionContext – I may be the new leader -
try and sync
102485 [main-EventThread] INFO org.apache.solr.cloud.SyncStrategy – Sync
replicas to http://192.168.1.104:7574/solr/c3_s1_replica2/
{code}
> killing a shard in one collection can result in leader election in a
> different collection
> -----------------------------------------------------------------------------------------
>
> Key: SOLR-5243
> URL: https://issues.apache.org/jira/browse/SOLR-5243
> Project: Solr
> Issue Type: Bug
> Reporter: Yonik Seeley
> Priority: Blocker
> Fix For: 4.5, 5.0
>
>
> Discovered while doing some more ad-hoc testing... if I create two
> collections with the same shard name and then kill the leader in one, it can
> sometimes cause a leader election in the other (leaving the first leaderless).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
