[jira] [Commented] (SOLR-13247) Incorrect shard placement during Collection creation

["Erick Erickson (JIRA)" <ji...@apache.org>]

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

Erick Erickson commented on SOLR-13247:
---------------------------------------

[~gus_heck][~bvd] 

WARNING: I haven't tried this personally. And it's not in the ref guide. There's a collection property you can set to revert to the old behavior. This isn't a fix, but might be a work-around. Set the cluster property "useLegacyReplicaAssignment" as below.

curl -X POST -H 'Content-type:application/json' --data-binary '
{"set-obj-property": {
    "defaults" : {
      "cluster": {
        "useLegacyReplicaAssignment":true
      }
    }
}}' http://localhost:8981/api/cluster

If it works for you, could you please confirm on this ticket?

> Incorrect shard placement during Collection creation
> ----------------------------------------------------
>
>                 Key: SOLR-13247
>                 URL: https://issues.apache.org/jira/browse/SOLR-13247
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: SolrCloud
>    Affects Versions: 7.6, 7.7
>            Reporter: Bram Van Dam
>            Priority: Major
>
> TL;DR; createNodeSet & shards combination is not being respected.
> I'm attempting to create a collection with multiple shards, but
> apparently the value of createNodeSet is not being respected and shards
> are being assigned to nodes seemingly at random.
> createNodeSet.shuffle is set to false, so that's not the cause.
> Furthermore, sometimes not all nodes in the request are used.
> Here's the create request, cleaned up for legibility. Note that the node names
> are IP addresses but I've removed the first 3 octets for legibility.
> admin/collections
> ?action=CREATE
> &name=collectionName
> &router.name=implicit
> &shards=collectionName1,collectionName2,collectionName3,collectionName4,collectionName5,collectionName6
> &maxShardsPerNode=1024
> &collection.configName=some_config
> &createNodeSet=171:8180_solr,172:8180_solr,173:8180_solr,177:8180_solr,179:8180_solr,179:8180_solr
> &createNodeSet.shuffle=false
> &waitForFinalState=true
> Note that I'm creating a collection with 6 shards across 5 nodes.
> Requested:
> collectionName1: 171:8180_solr
> collectionName2: 172:8180_solr
> collectionName3: 173:8180_solr
> collectionName4: 177:8180_solr
> collectionName5: 179:8180_solr
> collectionName6: 179:8180_solr
> Actual:
> collectionName1: 177:8180_solr
> collectionName2: 172:8180_solr
> collectionName3: 179:8180_solr
> collectionName4: 173:8180_solr
> collectionName5: 171:8180_solr
> collectionName6: 171:8180_solr
> Not a single shard ends up on the requested node.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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