I sent this over the weekend as well but it may have gotten lost in the test failures.
While researching (https://issues.apache.org/jira/browse/SOLR-11392) I ran into the following: The test is failing on jenkins with the following error: <h2>HTTP ERROR: 404</h2> <p>Problem accessing /solr/mainCorpus_shard2_replica_n3/update. Reason: <pre> Can not find: /solr/mainCorpus_shard2_replica_n3/update</pre></p> Notice this is looking for the "_n3" replica. What's odd about this is that only two replicas where created for this collection. From the test logs: [junit4] 2> 134364 INFO (OverseerStateUpdate-98710583079665671-127.0.0.1:33171_solr-n_0000000000) [n:127.0.0.1:33171_solr ] o.a.s.c.o.SliceMutator createReplica() { [junit4] 2> "operation":"ADDREPLICA", [junit4] 2> "collection":"mainCorpus", [junit4] 2> "shard":"shard1", [junit4] 2> "core":"mainCorpus_shard1_replica_n1", [junit4] 2> "state":"down", [junit4] 2> "base_url":"http://127.0.0.1:44379/solr";, [junit4] 2> "type":"NRT"} [junit4] 2> 134365 INFO (OverseerStateUpdate-98710583079665671-127.0.0.1:33171_solr-n_0000000000) [n:127.0.0.1:33171_solr ] o.a.s.c.o.SliceMutator createReplica() { [junit4] 2> "operation":"ADDREPLICA", [junit4] 2> "collection":"mainCorpus", [junit4] 2> "shard":"shard2", [junit4] 2> "core":"mainCorpus_shard2_replica_n2", [junit4] 2> "state":"down", [junit4] 2> "base_url":"http://127.0.0.1:45595/solr";, [junit4] 2> "type":"NRT"} So the question is why is the client looking for the third replica? Another odd thing with this failure is that it doesn't reproduce and I've never seen it locally. So this only happens on Jenkins. Anyone run across an issue like this before? Joel Bernstein http://joelsolr.blogspot.com/
