You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Mike Drob (Jira)" <ji...@apache.org> on 2021/04/05 20:12:00 UTC
[jira] [Reopened] (SOLR-15288) PRS replicas stay ACTIVE after a
new node is stopped
[ https://issues.apache.org/jira/browse/SOLR-15288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Drob reopened SOLR-15288:
------------------------------
Assignee: Ishan Chattopadhyaya
Ishan, I'm getting a reproducible test failure that git bisect claims started with b704dc628c2b949a16df501570fec591376a74fa (also seen on branch_8_8)
{{ant clean test -Dtestcase=CloudSolrClientTest -Dtests.seed=99D735A100387AC -Dtests.slow=true -Dtests.badapples=true -Dtests.locale=sk-SK -Dtests.timezone=Europe/Kiev -Dtests.asserts=true -Dtests.file.encoding=UTF-8}}
Can you take a look?
> PRS replicas stay ACTIVE after a new node is stopped
> -----------------------------------------------------
>
> Key: SOLR-15288
> URL: https://issues.apache.org/jira/browse/SOLR-15288
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 8.8.1
> Reporter: Ishan Chattopadhyaya
> Assignee: Ishan Chattopadhyaya
> Priority: Critical
> Fix For: 8.8.2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Steps to reproduce:
> https://issues.apache.org/jira/browse/SOLR-15288?focusedCommentId=17312808&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17312808
> ---- Older description (that refers to a bug when started multiple nodes starting in same dir, SOLR-15305 deals with that issue now ---
> After a PRS collection is created using a single node cluster, and a new node is added and a replica for that collection is placed on the new node, restarting that new node causes problems with replica states.
> Reproduce script:
> {code}
> # Start a fresh ZK on 2181
> # docker container prune -f && docker run -it -p 2181:2181 --name=zk1 -h zk1 zookeeper:3.5.6
> rm -rf server/logs/*
> bin/solr stop -all
> rm -rf server/solr/mycoll_shard1_replica_n1/ server/solr/mycoll_shard1_replica_n3/
> bin/solr -c -p 9000 -z localhost:2181
> curl "http://localhost:9000/solr/admin/collections?action=CREATE&name=mycoll&numShards=1&perReplicaState=true"
> bin/solr -c -p 9001 -z localhost:2181
> curl "http://localhost:9000/solr/admin/collections?action=ADDREPLICA&collection=mycoll&shard=shard1"
> bin/solr stop -p 9001
> bin/solr -c -p 9001 -z localhost:2181
> {code}
> Two problems:
> 1. Now look at the two replicas, both are down.
> 2. Also, as [~hitesh.khamesra] found out, the second replica stays ACTIVE (not DOWN) after the second node (9001) is stopped.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org