[
https://issues.apache.org/jira/browse/SOLR-11807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16517931#comment-16517931
]
Varun Thacker commented on SOLR-11807:
--------------------------------------
Okay so now I understand what happened. this was changed in 7.0 ( SOLR-11239 )
[~noble.paul] / [~shalinmangar] what do you guys think of the right solution
here for dealing with maxShardsPerNode=-1 while restoring a collection ? Add
the special handling there as well?
Also I don't understand a few things from SOLR-11239 . From that Jira there is
a comment saying
{quote}Firstly, {{maxShardsPerNode}} defaults to 1. So if anyone needs to host
more than 1 replica per node then they must specify {{maxShardsPerNode}} while
creating the collection via the collection API.
{quote}
This didn't change ? When I try adding a collection like this
{code:java}
admin/collections?action=create&name=test&numShards=4&replicationFactor=4{code}
I get an error
{code:java}
Cannot create collection test. Value of maxShardsPerNode is 1, and the number
of nodes currently live or live and part of your createNodeSet is 2. This
allows a maximum of 2 to be created. Value of numShards is 4, value of
nrtReplicas is 4, value of tlogReplicas is 0 and value of pullReplicas is 0.
This requires 16 shards to be created (higher than the allowed number){code}
Was this intentionally not addressed in that Jira?
> Restore Collection should reuse maxShardsPerNode specified during backup
> ------------------------------------------------------------------------
>
> Key: SOLR-11807
> URL: https://issues.apache.org/jira/browse/SOLR-11807
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Backup/Restore
> Reporter: Varun Thacker
> Assignee: Varun Thacker
> Priority: Minor
> Fix For: master (8.0), 7.5
>
> Attachments: SOLR-11807.patch, SOLR-11807.patch
>
>
> When you start Solr 6.6. and run the cloud example here's the log excerpt :
> {code:java}
> Connecting to ZooKeeper at localhost:9983 ...
> INFO - 2018-06-20 13:44:47.491;
> org.apache.solr.client.solrj.impl.ZkClientClusterStateProvider; Cluster at
> localhost:9983 ready
> ...
> Creating new collection 'gettingstarted' using command:
> http://localhost:8983/solr/admin/collections?action=CREATE&name=gettingstarted&numShards=2&replicationFactor=2&maxShardsPerNode=2&collection.configName=gettingstarted{code}
> maxShardsPerNode get's set to 2 .
>
> Compare this to Solr 7.3
> {code:java}
> INFO - 2018-06-20 13:55:33.823;
> org.apache.solr.client.solrj.impl.ZkClientClusterStateProvider; Cluster at
> localhost:9983 ready
> Created collection 'gettingstarted' with 2 shard(s), 2 replica(s) with
> config-set 'gettingstarted'{code}
> So something changed and now we no longer set maxShardsPerNode and it
> defaults to -1 .
>
> -1 has special handing while creating a collection ( it means max int ) .
> This special handling is not there while restoring a collection and hence
> this fails
> We should not set maxShardsPerNode to -1 in the first place
> Steps to reproduce:
> 1. ./bin/solr start -e cloud -noprompt : This creates a 2 node cluster and a
> gettingstarted collection which 2X2
> 2. Add 4 docs (id=1,2,3,4) with commit=true and openSearcher=true (default)
> 3. Call backup:
> [http://localhost:8983/solr/admin/collections?action=BACKUP&name=gettingstarted_backup&collection=gettingstarted&location=/Users/varunthacker/solr-7.1.0]
> 4. Call restore:
>
> [http://localhost:8983/solr/admin/collections?action=restore&name=gettingstarted_backup&collection=restore_gettingstarted&location=/Users/varunthacker/solr-7.1.0]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
