# Understand the impact on the document writing process after setting index.translog.durability=true
**URL:** https://discuss.elastic.co/t/understand-the-impact-on-the-document-writing-process-after-setting-index-translog-durability-true/385517
**Category:** Elasticsearch
**Created:** [March 19, 2026, 3:32am UTC](https://discuss.elastic.co/t/understand-the-impact-on-the-document-writing-process-after-setting-index-translog-durability-true/385517 "2026-03-19T03:32:51Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@mloine](https://discuss.elastic.co/u/mloine)
#### Post date: [March 19, 2026, 3:32am UTC](https://discuss.elastic.co/t/understand-the-impact-on-the-document-writing-process-after-setting-index-translog-durability-true/385517/1 "2026-03-19T03:32:51Z")
After setting index.translog.durability=true, the time to successfully respond to the client is whether to respond to the client as long as the primary shard is successful without shutting down the replicas, or to respond to the client after all replicas have responded successfully?
---
### Author:  [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [March 19, 2026, 6:17am UTC](https://discuss.elastic.co/t/understand-the-impact-on-the-document-writing-process-after-setting-index-translog-durability-true/385517/2 "2026-03-19T06:17:51Z")
Regardless of `index.translog.durability`, Elasticsearch responds to a write request after every [in-sync shard copy](https://www.elastic.co/blog/tracking-in-sync-shard-copies) has accepted the write (both primaries and replicas). This setting does not accept the value `true`, only `request` or `async`, but these just determine whether “accepted the write” includes having fsynced it to disk or not.