We have a webapp that has embedded solr integrated in it. It essentially handles creating separate index (core) per client and it is currently setup such that there can only be one index write operation per core. Say if we have 1 Million documents that needs be to Indexed, our app reads each document and writes it to index (using embedded solr library).
I am looking into ways to speed up indexing time and I was wondering if it would be possible to have our app run on multiple servers and each server process indexing docs concurrently. I was thinking of having Index storage on NFS that can be accessed by all servers. I am not entirely sure but reading through documentation my understanding is that we cannot have multiple index writers (even if they are running on different servers) write to same index directory simultaneously. is that correct? If there is a limitation on concurrent writes to same index directory then do i need to have each server build a separate index (more like a cores within core) and merge all the sub indexes into main index to speed up the indexing time? Please let me know if am heading in correct path or if there are better alternatives to speed up indexing time? -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-Index-Concurrency-Is-it-possible-to-have-multiple-threads-write-to-same-index-tp4002544.html Sent from the Solr - User mailing list archive at Nabble.com.
