# Rollback? ES 6?

**URL:** <https://discuss.elastic.co/t/rollback-es-6/85958>\
**Category:** Elasticsearch\
**Created:** [May 16, 2017, 2:47pm UTC](https://discuss.elastic.co/t/rollback-es-6/85958 "2017-05-16T14:47:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![billnbell](https://avatars.discourse-cdn.com/v4/letter/b/eb8c5e/32.png) [@billnbell](https://discuss.elastic.co/u/billnbell)\
**Post date:** [May 16, 2017, 2:47pm UTC](https://discuss.elastic.co/t/rollback-es-6/85958/1 "2017-05-16T14:47:21Z")

</div>

I read that ElasticSearch may never support rollback even though it has a tranlog. Why?

There are some interesting use cases when using:

begin\_tran()  
bunch of updates/inserts and possible rollback()  
commit\_tran()

---

<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:** [May 16, 2017, 3:44pm UTC](https://discuss.elastic.co/t/rollback-es-6/85958/2 "2017-05-16T15:44:33Z")

</div>

You can "simulate" such a behavior using a transactional queue system (ActiveMQ for example IIRC) and just read the commited queue to create a bulk and index in elasticsearch.

My 2 cents

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [May 16, 2017, 11:16pm UTC](https://discuss.elastic.co/t/rollback-es-6/85958/3 "2017-05-16T23:16:39Z")

</div>

While "translog" seems to resemble to a "transaction log" of the database theory world, the concept in ES is a bit different.

The translog is just a local write-ahead log file for the process of transmitting data from operation commands to disk. Like a metadata journal in a file system, it provides atomicity and durability, not all four properties of ACID. A single translog for a shard alone does not provide checkpoints for coordinated index-wide rollback. And in a distributed system, you have to provide also solutions for more complex situations, the challenges are described by the CAP theorem. This is where ES 6 sequence IDs will be an interesting topic, they can save a lot of work when shards must be recovered globally.

---

<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 13, 2017, 11:16pm UTC](https://discuss.elastic.co/t/rollback-es-6/85958/4 "2017-06-13T23:16:43Z")

</div>

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