Blocking or non-blocking model?

[Floyd Wu <fl...@gmail.com>]

Hi all,

After some investigating through source, I still can't sure that will Lucene
block other operatinos(such as query/add document) during merge process
being executed?

Seem that Lucene.Net-2.3.2 performed a different behavior wit
Lucene.Net-2.9.1.
When Lucene.Net-2.3.2 started to merge segments, write.lock file showed and
won't be deleted for a long long time.(at that point, indexes file is about
33GB and a client still added content but blocked); Upgrade to
Lucene.Net-2.9.1, things change, the write.lock file hardly showed and even
showed and it will be delete shortly.(but client still hit blocked)

http://www.gossamer-threads.com/lists/lucene/java-dev/45651?search_string=concurrent%20merge
;

The above discussion is my start point.
Can someone tell me what is the final conclusion of current .Net
implementation. Is blocking model or non-blocking model?

Thanks

Floyd