Hi, First off, as a new user of Solr, I'm extremely impressed with the Solr service and accompanying admin tool. Thank you very much to those who have contributed!
My environment: Windows 2003 R2 x64 edition server 4gb RAM Java 6 update 18 - 64 bit Tomcat 6.0.18 Solr 1.3 Single Index / No replication I have multiple SolrJ clients that will be sending small update requests but should be staggered in time to prevent concurrent updates. However, to add additional margin of error, I would like to apply the safest locking mechanism possible to avoid corruption. We have a single solr server. From what I'm reading in the solrconfig.xml, I'm gathering that perhaps the NativeFSLockFactory would be more appropriate than the default SingleInstanceLockFactory or the SimpleFSLockFactory. Questions: 1) Is NativeFSLockFactory the preferred index locking mechanism in this scenario? 2) Does the NativeFSLockFactory work on the windows platforms? 3) Does the NativeFSLockFactory require any code changes for solrj clients or is it transparent to that layer? 4) What is the expected behavior if a client requests an update and there is a lock from a previous client? What is the granularity of the lock? Please let me know if I can clarify anything... thanks for your time. Kind Regards, Alan May
