: I have two cores in different machines which are referring to the same data directory.
this isn't really considered a supported configuration ... both solr instances are going to try and "own" the directory for updating, and unless you do somethign special to ensure only one has control you are going to have problems... : below error. HTTP Status 500 - java.io.FileNotFoundException: : \\SolrShare\CollectionSet2\English\Auction\Auction0\index\_c.fdt (The : system cannot find the file specified) java.lang.RuntimeException: : java.io.FileNotFoundException: : \\SolrShare\CollectionSet2\English\Auction\Auction0\index\_c.fdt (The ...like this. one core is mucking with the files in a way the other core doesn't know about. : I have changed lockType to simple and none, but still no luck… : Could you please correct me if I am doing wrong? "none" isn't going to help you -- it's just going to make the problem worse (two misconfigured instances of Solr in the same JVM could corrupt eachother with lockType=none). "simple" is only going to help you on some filesystems -- sicne you said these two solr instances are running on different machines, that implies NFS (or something like it) and SimpleFSLockFactory doesn't work reliably in those cases. If you want to get something like this working, you'll probably need to setup your own network based lockType (instead of relying on the filesystem) -Hoss
