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

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

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

JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/SOLR-11479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hoss Man updated SOLR-11479:
----------------------------
    Attachment: SOLR-11479.patch

here's a (test only) patch demonstrating the problem ... really straight forward addition to CollectionsAPISolrJTest...

{code}
  @Test
  public void testAddReplicaWithCoreNodeNameProp() throws Exception {

    final String collectionName = "solrj_replica_explicit_coreNodeName";
    CollectionAdminRequest.createCollection(collectionName, "conf", 1, 2)
      .process(cluster.getSolrClient());

    final String coreNodeName = "user_assigned_node_name";
   
    CollectionAdminResponse response = CollectionAdminRequest.addReplicaToShard(collectionName, "shard1")
      .withProperty(CoreDescriptor.CORE_NODE_NAME, coreNodeName)
      .process(cluster.getSolrClient());
   
    assertEquals(0, response.getStatus());
    assertTrue(response.isSuccess());
   
    Replica newReplica = grabNewReplica(response, getCollectionState(collectionName));
    assertTrue(newReplica.getName().equals(coreNodeName));
  }

{code}

> Collections API: ADDREPLICA fails if you try to specify property.coreNodeName=foo
> ---------------------------------------------------------------------------------
>
>                 Key: SOLR-11479
>                 URL: https://issues.apache.org/jira/browse/SOLR-11479
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public)
>            Reporter: Hoss Man
>         Attachments: SOLR-11479.patch
>
>
> 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)
> {noformat}
>    [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
> {noformat}
> ...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????



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]