For the SolrCloud experts here... I'm looking at this LockLevel: org.apache.solr.common.params.CollectionParams.CollectionAction#ADDREPLICAPROP I'm doubtful that replica property manipulation needs a mutual exclusion lock against other things in the cluster. I believe a collection's state is modified in a CAS manner with a retry if the basis of the state version (the znode version of the collection's state) is different. Adding/removing properties seems simple/atomic enough so as to not need a lock level. Am I missing something?
This is in the context of a PR that will change waitForFinalState in order to help a test: https://github.com/apache/solr/pull/3684 ~ David Smiley Apache Lucene/Solr Search Developer http://www.linkedin.com/in/davidwsmiley
