[
https://issues.apache.org/jira/browse/SOLR-9484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15492444#comment-15492444
]
ASF subversion and git services commented on SOLR-9484:
-------------------------------------------------------
Commit 34b1f65c4d0d884528620c96430096539e9fb743 in lucene-solr's branch
refs/heads/branch_6x from [~shalinmangar]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=34b1f65 ]
SOLR-9484: The modify collection API should wait for the modified properties to
show up in the cluster state
(cherry picked from commit 70fd627)
> The modify collection API should wait for the modified properties to show up
> in the cluster state
> -------------------------------------------------------------------------------------------------
>
> Key: SOLR-9484
> URL: https://issues.apache.org/jira/browse/SOLR-9484
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Affects Versions: 6.2
> Reporter: Shalin Shekhar Mangar
> Assignee: Cao Manh Dat
> Labels: difficulty-easy, impact-medium
> Fix For: 6.3, master (7.0)
>
> Attachments: SOLR-9484.patch, SOLR-9484.patch
>
>
> The modify collection API doesn't wait for the updated properties to show up
> in the cluster state. Say you increase the maxShardsPerNode for a collection
> using this API, if you try to add a replica immediately after modify
> collection API returns then the overseer sometimes doesn't see the updated
> property and refuses to add a new replica.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
