# Elasticsearch with guaranteed transactional consistency at all times

**URL:** <https://discuss.elastic.co/t/elasticsearch-with-guaranteed-transactional-consistency-at-all-times/193013>\
**Category:** Elasticsearch\
**Created:** [July 31, 2019, 2:00am UTC](https://discuss.elastic.co/t/elasticsearch-with-guaranteed-transactional-consistency-at-all-times/193013 "2019-07-31T02:00:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![schamaraj](https://avatars.discourse-cdn.com/v4/letter/s/35a633/32.png) [@schamaraj](https://discuss.elastic.co/u/schamaraj)\
**Post date:** [July 31, 2019, 2:00am UTC](https://discuss.elastic.co/t/elasticsearch-with-guaranteed-transactional-consistency-at-all-times/193013/1 "2019-07-31T02:00:58Z")

</div>

We moved from Oracle DB to a clustered (all master eligible, all data eligible) Elasticsearch 2.4.1 without really changing the data model too much. We recently found an issue that when the network latency is higher, the Elasticsearch nodes go out of sync and the micro-services read stale data and cause inconsistencies in the state machine.

The product requires guaranteed transactional consistency at all times - and Elasticsearch was probably not the correct choice of database

However, we are at a stage where changing the DB may be a costly option

Is there any set of configurations (API options) that can be done to achieve guaranteed transactional consistency at all times?

Is there any way to set up Elasticsearch as a master-slave so that only one node is active at any time and all the primary shards are located on the same node - and the slave node is just for high availability?

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [July 31, 2019, 6:03am UTC](https://discuss.elastic.co/t/elasticsearch-with-guaranteed-transactional-consistency-at-all-times/193013/2 "2019-07-31T06:03:22Z")

</div>

Elasticsearch 2.4.1 is positively ancient and has a few known and [documented](https://www.elastic.co/guide/en/elasticsearch/resiliency/current/index.html) issues that might cause this. You should upgrade.

---

<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 28, 2019, 6:03am UTC](https://discuss.elastic.co/t/elasticsearch-with-guaranteed-transactional-consistency-at-all-times/193013/3 "2019-08-28T06:03:37Z")

</div>

Closed on August 28, 2019, 6:03am UTC

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