[
https://issues.apache.org/jira/browse/SOLR-17963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18030958#comment-18030958
]
ASF subversion and git services commented on SOLR-17963:
--------------------------------------------------------
Commit 18778f56f72120b46894e941f40d0e6786444d31 in solr's branch
refs/heads/main from David Smiley
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=18778f56f72 ]
SOLR-17963: Don't lock: COLLECTIONPROP, ADDREPLICAPROP, DELETEREPLICAPROP
(#3786)
These SolrCloud commands no longer aquire locks (waiting or blocking on other
commands that do):
COLLECTIONPROP, ADDREPLICAPROP, DELETEREPLICAPROP.
They are atomic/transactional and are not believed to interfere with commands
that need locks.
> Don't lock replicas for ADDREPLICAPROP, other PROP
> --------------------------------------------------
>
> Key: SOLR-17963
> URL: https://issues.apache.org/jira/browse/SOLR-17963
> Project: Solr
> Issue Type: Task
> Components: SolrCloud
> Reporter: David Smiley
> Priority: Major
> Labels: pull-request-available
> Fix For: 10.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Propose that ADDREPLICAPROP & DELETEREPLICAPROP & COLLECTIONPROP do not
> acquire a replica/collection lock, thus do not acquire higher level locks in
> the tree either. They operate atomically.
> There is some risk of interference with BALANCESHARDUNIQUE if one were to
> send property manipulation commands concurrently with that command... but
> it'd hard to imagine that ever being sensible anyway.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
