On 3/23/2016 6:00 AM, Raveendra Yerraguntla wrote: > I am using Solr 5.4 in solr cloud mode in a 8 node cluster. Used the > replication factor of 1 for creating the index, then switched to > replication factor > 1 for redundancy. With replication factor > 1, and > tried to do indexing for incremental. When the incremental indexing > happens - getting a stack trace with the root cause pointing to write.lock > is not available. Further analysis found that there is only one write.lock > across all shards (leader and replicas). > > But with replication factor of 1 , I could see write.lock across all nodes.
Did you see my reply on the dev list, sent before I told you that your question belonged on this list? In that reply I told you that replicationFactor will have no effect after you create your collection. It also cannot cause problems with the write.lock file. I also said this: There are three major reasons for a problem with write.lock. 1) Solr is crashing and leaving the write.lock file behind. 2) You are trying to share an index directory between more than one core or Solr instance. 3) You are trying to run with your index data on a network filesystem like NFS. Thanks, Shawn
