[
https://issues.apache.org/jira/browse/SOLR-5240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13765922#comment-13765922
]
Yonik Seeley commented on SOLR-5240:
------------------------------------
I was doing some ad-hoc testing of the current state of cloud when I ran across
this bug.
Steps to reproduce:
{code}
# our standard cloud bootstrap
java -Dbootstrap_confdir=./solr/collection1/conf -Dcollection.configName=c1
-DzkRun -DnumShards=2 -jar start.jar
# create a new collection
curl
"http://localhost:8983/solr/admin/collections?action=CREATE&name=c2&replicationFactor=4&router=implicit&shards=s1&maxShardsPerNode=100";
# now kill the server (CTRL-C on the console or whatever)
# now restart the server
java -DzkRun -jar start.jar
#and the admin console isn't responsive, and you see this in the logs...
12628 [coreLoadExecutor-4-thread-2] INFO
org.apache.solr.cloud.ShardLeaderElectionContext – Waiting until we see more
replicas up for shard s1: total=4 found=3 timeoutin=179999
1
32701 [coreLoadExecutor-4-thread-2] INFO
org.apache.solr.cloud.ShardLeaderElectionContext – Waiting until we see more
replicas up for shard s1: total=4 found=3 timeoutin=159926
[...]
{code}
> SolrCloud node doesn't (quickly) come all the way back
> ------------------------------------------------------
>
> Key: SOLR-5240
> URL: https://issues.apache.org/jira/browse/SOLR-5240
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.5
> Reporter: Yonik Seeley
> Fix For: 4.5
>
>
> Killing a single node and bringing it back up can result in "waiting until we
> see more replicas up..."
--
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]
