You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Erick Erickson (Jira)" <ji...@apache.org> on 2020/10/16 20:08:00 UTC

[jira] [Commented] (SOLR-13654) Scary jenkins failure related to collection creation: "non legacy mode coreNodeName missing"

    [ https://issues.apache.org/jira/browse/SOLR-13654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215631#comment-17215631 ] 

Erick Erickson commented on SOLR-13654:
---------------------------------------

[~hossman] I think this can be closed? At least that error cannot be thrown now since that code was removed in SOLR-12823

> Scary jenkins failure related to collection creation: "non legacy mode coreNodeName missing"
> --------------------------------------------------------------------------------------------
>
>                 Key: SOLR-13654
>                 URL: https://issues.apache.org/jira/browse/SOLR-13654
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Chris M. Hostetter
>            Priority: Major
>         Attachments: thetaphi_Lucene-Solr-8.2-Linux_452.log.txt
>
>
> A recent SplitShardTest jenkins failure has a perplexing error that i've been updable to reproduce...
> {noformat}
>    [junit4]    > Throwable #1: org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error from server at http://127.0.0.1:36447/_bx/t: Underlying core creation failed while creating collection: shardSplitWithRule_link
> {noformat}
> ...this exception is thrown when attempting to create a brand new 1x2 collection (prior to any splitting) using the following rule/request...
> {noformat}
>     CollectionAdminRequest.Create createRequest = CollectionAdminRequest.createCollection(collectionName, "conf1", 1, 2)
>         .setRule("shard:*,replica:<2,node:*");
> {noformat}
> ...the logs indicate that the specific problem is that the CREATE SolrCore commands aren't inlcuding a 'coreNodeName' which is mandatory because this is a "non legacy" clusuter...
> {noformat}
>    [junit4]   2> 1090551 ERROR (OverseerThreadFactory-6577-thread-5) [     ] o.a.s.c.a.c.OverseerCollectionMessageHandler Error from shard: http://127.0.0.1:36447/_bx/t
>    [junit4]   2>           => org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error from server at http://127.0.0.1:36447/_bx/t: Error CREATEing SolrCore 'shardSplitWithRule_link_shard1_replica_n1': non legacy mode coreNodeName missing {collection.configName=conf1, numShards=1, shard=shard1, collection=shardSplitWithRule_link, replicaType=NRT}
>    [junit4]   2>        at org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:656)
>    [junit4]   2> org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error from server at http://127.0.0.1:36447/_bx/t: Error CREATEing SolrCore 'shardSplitWithRule_link_shard1_replica_n1': non legacy mode coreNodeName missing {collection.configName=conf1, numShards=1, shard=shard1, collection=shardSplitWithRule_link, replicaType=NRT}
>    [junit4]   2>        at org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:656) ~[java/:?]
>    [junit4]   2>        at org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:262) ~[java/:?]
>    [junit4]   2>        at org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:245) ~[java/:?]
>    [junit4]   2>        at org.apache.solr.client.solrj.SolrClient.request(SolrClient.java:1274) ~[java/:?]
>    [junit4]   2>        at org.apache.solr.handler.component.HttpShardHandlerFactory$1.request(HttpShardHandlerFactory.java:176) ~[java/:?]
>    [junit4]   2>        at org.apache.solr.handler.component.HttpShardHandler.lambda$submit$0(HttpShardHandler.java:199) ~[java/:?]
>    [junit4]   2>        at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
> {noformat}
> ...so how/why is the Overseer generating CREATE core commands w/o coreNodeName params ????
> Is this a race condition between the test setting legacyCloud=false and the Overseer processing the CREATE collection Op?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org