# Index.translog.durability async

**URL:** <https://discuss.elastic.co/t/index-translog-durability-async/92646>\
**Category:** Elasticsearch\
**Created:** [July 11, 2017, 12:57pm UTC](https://discuss.elastic.co/t/index-translog-durability-async/92646 "2017-07-11T12:57:49Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alex\_Davidovich](https://avatars.discourse-cdn.com/v4/letter/a/b9e5f3/32.png) [@Alex\_Davidovich](https://discuss.elastic.co/u/Alex_Davidovich)\
**Post date:** [July 11, 2017, 12:57pm UTC](https://discuss.elastic.co/t/index-translog-durability-async/92646/1 "2017-07-11T12:57:49Z")

</div>

In case an index.translog.durability is set to async and process is killed, but OS is up and running.  
Will there be any data loss?  
From what I understand, only in case of OS reboot/ power loss/ hardware issues, there will be a data loss.  
Am I right?

Thanks

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [July 11, 2017, 1:13pm UTC](https://discuss.elastic.co/t/index-translog-durability-async/92646/2 "2017-07-11T13:13:27Z")

</div>

If you change the translog durability setting to `async` yes you can have data loss in case of hardware issues but I'd guess that it can also happen in case of hard kill of the jvm..  
Why do you want to change it? Speed?

---

<div class="post-metadata">

**Author:** ![Alex\_Davidovich](https://avatars.discourse-cdn.com/v4/letter/a/b9e5f3/32.png) [@Alex\_Davidovich](https://discuss.elastic.co/u/Alex_Davidovich)\
**Post date:** [July 11, 2017, 1:15pm UTC](https://discuss.elastic.co/t/index-translog-durability-async/92646/3 "2017-07-11T13:15:21Z")

</div>

> [@dadoonet](#):
>
> If you change the translog durability setting to async yes you can have data loss in case of hardware issues but I'd guess that it can also happen in case of hard kill of the jvm..

Research purposes only, thanks

---

<div class="post-metadata">

**Author:** ![Alex\_Davidovich](https://avatars.discourse-cdn.com/v4/letter/a/b9e5f3/32.png) [@Alex\_Davidovich](https://discuss.elastic.co/u/Alex_Davidovich)\
**Post date:** [July 12, 2017, 9:23am UTC](https://discuss.elastic.co/t/index-translog-durability-async/92646/4 "2017-07-12T09:23:43Z")

</div>

By "Kill of the jvm" you mean to kill hard the ES process?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [July 12, 2017, 11:28am UTC](https://discuss.elastic.co/t/index-translog-durability-async/92646/5 "2017-07-12T11:28:35Z")

</div>

Yeah. Something like a `kill -9` (`SIGKILL`). Not sure how the JVM behaves in that case.

---

<div class="post-metadata">

**Author:** ![Alex\_Davidovich](https://avatars.discourse-cdn.com/v4/letter/a/b9e5f3/32.png) [@Alex\_Davidovich](https://discuss.elastic.co/u/Alex_Davidovich)\
**Post date:** [July 17, 2017, 8:15am UTC](https://discuss.elastic.co/t/index-translog-durability-async/92646/6 "2017-07-17T08:15:13Z")

</div>

@dadoonet - Another question, if I may:

Can this configuration (async), cause translog corruption? And ES will have a problem recovering?  
Or can only cause loss of data that was not fsynced?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 14, 2017, 8:15am UTC](https://discuss.elastic.co/t/index-translog-durability-async/92646/7 "2017-08-14T08:15:14Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.