[jira] [Commented] (SOLR-12750) Migrate API should lock the collection instead of shard

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on SOLR-12750:
--------------------------------------------------------

Commit 84683b6aa072459b364c62e71abd526cdcf8e117 in lucene-solr's branch refs/heads/master from [~shalinmangar]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=84683b6 ]

SOLR-12750: Migrate API should lock the collection instead of shard


> 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
>            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