Update durability vs Solr

Clinton_Gormley · July 16, 2012, 5:21pm

Hi Mike

Peeking at the sources it looks like there is a buffering option (add
to the log after N changes/MB have buffered up in RAM) and a
non-buffering option ... so I'm wondering what the default is.

It looks like the default is 64kB:

github.com/elastic/elasticsearch

Translog: When not sync'ing on each operation, buffer writes

opened 10:14PM - 17 Dec 11 UTC

closed 10:19PM - 17 Dec 11 UTC

kimchy

>enhancement v0.19.0.RC1

Buffer writes when not sync'ing on each operation. Sync will cause flush and syn…c. Buffering will be on by default if not sync'ing on each operation. Settings (can be dynamically updated using update settings API): - `index.translog.fs.type`: Either `simple` or `buffered`. Defaults to `buffer` if not sync'ing on each operation. - `index.translog.fs.buffer_size`: The buffer size, defaults to `64k`.

clint

Topic		Replies	Views
Details of how transaction log is managed during indexing Elasticsearch	7	2955	July 6, 2017
Translog Settings Elasticsearch	2	947	July 5, 2017
Translog Durability Elasticsearch	2	402	June 22, 2018
Persistent transaction log Elasticsearch	3	760	July 6, 2017
Elasticesearch 7.6.2 translog overflow issue Elasticsearch	10	865	December 28, 2020

Update durability vs Solr

Related topics