does lucene.net control churned threads accessing same index, indexing while searching?

when controlling lucene.net asp.net, i suspect web ask trigger an transform index while another web ask behaving search. does lucene.net have built ability control indicate access, i have control it, prevaricate "being used another process" errors?

edit: after reading docs experimentation, i cruise i've learned: there twin issues, thread reserve concurrency. multithreading "safe" can't anything bad index. but, it's stable during cost only vigilant carrying close index during time. second vigilant along pitch an exception. so, can't leave hunt open design author another thread means transform index. thread bustling updating index, following perplexing emanate path-finder fail.

also, searchers index during open it, keep around, transform index, won't updates.

i wanted searchers latest updates.

my design, seems operative far, writers searchers share lock, don't destroy - only wait - until tide hunt done.