You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Ishan Chattopadhyaya (Jira)" <ji...@apache.org> on 2021/04/01 02:33:00 UTC

[jira] [Created] (SOLR-15305) Multiple nodes from same directory causes bizarre SolrCloud errors

Ishan Chattopadhyaya created SOLR-15305:
-------------------------------------------

             Summary: Multiple nodes from same directory causes bizarre SolrCloud errors
                 Key: SOLR-15305
                 URL: https://issues.apache.org/jira/browse/SOLR-15305
             Project: Solr
          Issue Type: Bug
      Security Level: Public (Default Security Level. Issues are Public)
            Reporter: Ishan Chattopadhyaya


Here's a spinoff from SOLR-15288.

After a collection is created using a single node cluster, and a new node is added (off the same directory) 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"
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 (in the Admin UI), both are down.
2. 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