[SOLR-11479] Collections API: ADDREPLICA fails if you try to specify property.coreNodeName=foo

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: Chris M. Hostetter
• Created: 12/Oct/17 18:20
• Updated: 08/Jun/19 15:16

Description

if you attempt to specify a property.coreNodeName param when using the Collection API's action=ADDREPLICA the request will fail – the underlying cause of the failure (in the logs for the node where the underlying Core Admin CREATECORE request is routed) seems like a perplexing chicken/egg problem...

(the various names in the error below are from a test patch i'll attach shortly)

   [junit4]   2> Caused by: org.apache.solr.common.SolrException: Unable to create core [solrj_replica_explicit_coreNodeName_shard1_replica_n5]
   [junit4]   2> 	at org.apache.solr.core.CoreContainer.createFromDescriptor(CoreContainer.java:1049)
   [junit4]   2> 	at org.apache.solr.core.CoreContainer.create(CoreContainer.java:947)
   [junit4]   2> 	... 34 more
   [junit4]   2> Caused by: org.apache.solr.common.SolrException: coreNodeName user_assigned_node_name does not exist in shard shard1: DocCollection(solrj_replica_explicit_coreNodeName//collections/solrj_replica_explicit_coreNodeName/state.json/7)={
...
   [junit4]   2> 11157 INFO  (qtp1977346252-47) [n:127.0.0.1:51786_solr c:solrj_replica_explicit_coreNodeName s:shard1 r:user_assigned_node_name x:solrj_replica_explicit_coreNodeName_shard1_replica_n5] o.a.s.s.HttpSolrCall [admin] webapp=null path=/admin/cores params={qt=/admin/cores&coreNodeName=core_node6&collection.configName=conf&name=solrj_replica_explicit_coreNodeName_shard1_replica_n5&property.coreNodeName=user_assigned_node_name&action=CREATE&collection=solrj_replica_explicit_coreNodeName&shard=shard1&wt=javabin&version=2&replicaType=NRT} status=400 QTime=3009

...the CREATE core action is failing because the cloud shard we want to ADDREPLICA to says that a replica with that coreNodeName doesn't exist????

Issue Links

• relates to: SOLR-11469 LeaderElectionContextKeyTest has flawed logic: 50% of the time it checks the wrong shard's elections