[GitHub] [lucenenet] mikeplacko commented on issue #494: IndexReader locks files

[GitBox <gi...@apache.org>]

mikeplacko commented on issue #494:
URL: https://github.com/apache/lucenenet/issues/494#issuecomment-864061910


   I think the negative side effect comes into play when you want to reset the search index programmatically by deleting all the index files. IIS can still be generating traffic, searches from users, while the writer process is trying to delete all those files before re-indexing. 
   My example was manual, as its easy to reproduce by just leaving the reader alive and hard to reproduce in normal operation because the reader is only alive a very short time. But it is happening under load in our application. The reader has those files locked and the other process cannot delete them to reset the index. 
   Maybe I can come up with a way to turn off searching in IIS while its trying to reset as a workaround but I think the better solution would be if Lucene.NET had a command for this. Literally Reset, which deletes everything thread safe. Maybe that's already available and I missed it?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org