You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shalin Shekhar Mangar (JIRA)" <ji...@apache.org> on 2018/10/03 11:09:00 UTC
[jira] [Resolved] (SOLR-12750) Migrate API should lock the
collection instead of shard
[ https://issues.apache.org/jira/browse/SOLR-12750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shalin Shekhar Mangar resolved SOLR-12750.
------------------------------------------
Resolution: Fixed
Assignee: Shalin Shekhar Mangar
> Migrate API should lock the collection instead of shard
> -------------------------------------------------------
>
> Key: SOLR-12750
> URL: https://issues.apache.org/jira/browse/SOLR-12750
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Reporter: Shalin Shekhar Mangar
> Assignee: Shalin Shekhar Mangar
> Priority: Major
> Fix For: 7.6, master (8.0)
>
>
> The Migrate API acquires the lock at the shard level and not even all of the relevant ones because the API can affect many shards and that information is not available at the time when the locking decisions are made. It is best if the Migrate API locks the entire collection instead of shard.
--
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