During experiments with Manticore Search I faced with strange behavior (use latest version on Windows with default settings).
I created rt index with rt_mem_limit=‘1Gb’ and one text field by the following command via mysql:
create table test_def(content text) rt_mem_limit=‘1G’;
My test inserts new records into this index in 10 threads via mysql connector.
When RAM chunk becomes full and saves into disk execution of new inserts stalls approximately on 9 minutes. And according to log saving of chunks to disk consumes these 9 minutes:
rt: index test_def: diskchunk 8(1), segments 32 saved in 530.809 sec
rt: index test_def: diskchunk 9(2), segments 32 saved in 528.586 sec
But actually chunk files are created by several seconds and then nothing happened to them (they are not changed). And no other disk I/O operations performed:
So what really happens with searchd process after saving chunk to files? What can be a reason of such behavior? Why it logs that all this time it saves chunk to disk?