# How to transport the translog to the not primary shard in async mode

**URL:** <https://discuss.elastic.co/t/how-to-transport-the-translog-to-the-not-primary-shard-in-async-mode/86345>\
**Category:** Elasticsearch\
**Created:** [May 19, 2017, 2:09am UTC](https://discuss.elastic.co/t/how-to-transport-the-translog-to-the-not-primary-shard-in-async-mode/86345 "2017-05-19T02:09:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![chixuan777](https://avatars.discourse-cdn.com/v4/letter/c/e95f7d/32.png) [@chixuan777](https://discuss.elastic.co/u/chixuan777)\
**Post date:** [May 19, 2017, 2:09am UTC](https://discuss.elastic.co/t/how-to-transport-the-translog-to-the-not-primary-shard-in-async-mode/86345/1 "2017-05-19T02:09:24Z")

</div>

we allow the not primary shard lose some data.(low consistency requirment)  
Can we config something to let the bulk request just return success after the primary shard write successful, and there will be another thread to transport the data to the replications in async mode?

---

<div class="post-metadata">

**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\
**Post date:** [May 19, 2017, 2:20am UTC](https://discuss.elastic.co/t/how-to-transport-the-translog-to-the-not-primary-shard-in-async-mode/86345/2 "2017-05-19T02:20:51Z")

</div>

No, this is not possible.

---

<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:** [June 16, 2017, 2:20am UTC](https://discuss.elastic.co/t/how-to-transport-the-translog-to-the-not-primary-shard-in-async-mode/86345/3 "2017-06-16T02:20:56Z")

</div>

Closed on June 16, 2017, 2:20am UTC

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