[
https://issues.apache.org/jira/browse/SOLR-17963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated SOLR-17963:
--------------------------------
Description:
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.
was:
Propose that ADDREPLICAPROP & DELETEREPLICAPROP do not acquire a replica 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.
> 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
>
> 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]
