What happens inside index.blocks?


(Andrej) #1

Hi,

I was wondering if someone could give me an inside view on whats happening
when I set index.blocks.write or index.blocks.read to true. Are
writing/reading threads stopped, should I gain search/indexing performance?
Is refreshing disabled when blocks.write is set? Or am I just safe that
those operations are not performed?

Thanks!
Andrej

--


Performance changes when setting index.blocks.write / read_only?
(BillyEm) #2

Have you checked the index writer in Lucene 3.5.x? Since Lucene is now
transacted it is possible for an operation to have a reference (or links to
a reference). While other blocks are being committed and becoming ver+1.
What to do to preserve currency with the beginning of the operation? Block
a read on transacted write operations, or block a write on transacted Read
operations. Once the operation completes the block/lock/synchronization is
released and the waiting (if set so) read or write can proceed.

whaddya think? Is that it? It should be very tightly scoped in the ES
codebase and easy to find?

On Tuesday, October 2, 2012 3:52:02 AM UTC-4, Andrej Rosenheinrich wrote:

Hi,

I was wondering if someone could give me an inside view on whats happening
when I set index.blocks.write or index.blocks.read to true. Are
writing/reading threads stopped, should I gain search/indexing performance?
Is refreshing disabled when blocks.write is set? Or am I just safe that
those operations are not performed?

Thanks!
Andrej

--


(system) #3