2013-08-28 19:24:34 -04:00
|
|
|
[[index-modules-translog]]
|
|
|
|
|
== Translog
|
|
|
|
|
|
|
|
|
|
Each shard has a transaction log or write ahead log associated with it.
|
|
|
|
|
It allows to guarantee that when an index/delete operation occurs, it is
|
|
|
|
|
applied atomically, while not "committing" the internal Lucene index for
|
|
|
|
|
each request. A flush ("commit") still happens based on several
|
|
|
|
|
parameters:
|
|
|
|
|
|
2014-07-31 08:06:06 -04:00
|
|
|
`index.translog.flush_threshold_ops`::
|
2013-08-28 19:24:34 -04:00
|
|
|
|
2014-07-31 08:06:06 -04:00
|
|
|
After how many operations to flush. Defaults to `unlimited`.
|
2013-08-28 19:24:34 -04:00
|
|
|
|
2014-07-31 08:06:06 -04:00
|
|
|
`index.translog.flush_threshold_size`::
|
2014-01-07 13:58:16 -05:00
|
|
|
|
2015-01-19 15:52:29 -05:00
|
|
|
Once the translog hits this size, a flush will happen. Defaults to `512mb`.
|
2014-07-31 08:06:06 -04:00
|
|
|
|
|
|
|
|
`index.translog.flush_threshold_period`::
|
|
|
|
|
|
|
|
|
|
The period with no flush happening to force a flush. Defaults to `30m`.
|
|
|
|
|
|
|
|
|
|
`index.translog.interval`::
|
|
|
|
|
|
|
|
|
|
How often to check if a flush is needed, randomized
|
2014-01-07 13:58:16 -05:00
|
|
|
between the interval value and 2x the interval value. Defaults to `5s`.
|
2014-07-31 08:06:06 -04:00
|
|
|
|
|
|
|
|
`index.gateway.local.sync`::
|
|
|
|
|
|
|
|
|
|
How often the translog is ++fsync++ed to disk. Defaults to `5s`.
|
|
|
|
|
|
2013-08-28 19:24:34 -04:00
|
|
|
|
|
|
|
|
Note: these parameters can be updated at runtime using the Index
|
|
|
|
|
Settings Update API (for example, these number can be increased when
|
|
|
|
|
executing bulk updates to support higher TPS)
|
