Long-running merges are an issue with large indexes due to the CPU and
I/O overhead required to perform the merge, but there are a few things
you can do to reduce that time:
1) Create a custom merge policy to give you control over when merges
occur and what segments are merged
2) Shard your index into smaller pieces that are searched together using
a MultiSearcher - this will keep your indexes smaller.
From: Floyd Wu
Sent: Monday, March 08, 2010 1:45 AM
Subject: About processing handling during merge time
I have a problem that my index files is 33.4gb now, and when I insert
index through Lucene.Net few times. Lucene will execute merge index
automatically. The problem is during merge executed, writer.lock file
be created and all operations such as read/write index files were all
(for a long time and there were no any status or flag to know Lucene
executeing merge process.)
Are there any solutions to avoid this "long time lock" situation?
Thanks in advanced.