Skip to content

Clarify consequence of translog async setting #44020

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 5, 2019
Merged

Clarify consequence of translog async setting #44020

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c2eaafa
Clarify consequence of translog async setting
dnhatn Jul 5, 2019
91d5d1a
Yannick’s suggestion
dnhatn Jul 5, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions docs/reference/index-modules/translog.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,8 +26,9 @@ although this is rarely needed.
=== Translog settings

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
since the previous translog commit will be lost.
++fsync++ed and committed. In the event of a hardware failure or an operating
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,
update, or bulk request to the client after the translog has been successfully
Expand Down Expand Up @@ -59,7 +60,7 @@ update, or bulk request. This setting accepts the following parameters:
`async`::

`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.
--

Expand Down