honeymoose/OpenSearch
1
0
Fork 0
mirror of https://github.com/honeymoose/OpenSearch.git synced 2025-02-22 21:05:23 +00:00
Code Issues Packages Projects Releases Wiki Activity

Clarify consequence of translog async setting (#44020)

Browse Source 
Relates #43915
This commit is contained in:
Nhat Nguyen 2019-07-05 13:55:25 -04:00
parent a831d4707c
commit 8bfe18477e
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/reference/index-modules/translog.asciidoc
View File

@ -26,8 +26,9 @@ although this is rarely needed.
=== Translog settings === Translog settings
The data in the translog is only persisted to disk when the translog is The data in the translog is only persisted to disk when the translog is
++fsync++ed and committed. In the event of hardware failure, any data written ++fsync++ed and committed. In the event of a hardware failure or an operating
since the previous translog commit will be lost. system crash or a JVM crash or a shard failure, any data written since the
previous translog commit will be lost.
By default, `index.translog.durability` is set to `request` meaning that Elasticsearch will only report success of an index, delete, By default, `index.translog.durability` is set to `request` meaning that Elasticsearch will only report success of an index, delete,
update, or bulk request to the client after the translog has been successfully update, or bulk request to the client after the translog has been successfully
@ -59,7 +60,7 @@ update, or bulk request. This setting accepts the following parameters:
`async`:: `async`::
`fsync` and commit in the background every `sync_interval`. In `fsync` and commit in the background every `sync_interval`. In
the event of hardware failure, all acknowledged writes since the last the event of a failure, all acknowledged writes since the last
automatic commit will be discarded. automatic commit will be discarded.
-- --