# About TranslogWriter.assertNoSeqNumberConflict

**URL:** <https://discuss.elastic.co/t/about-translogwriter-assertnoseqnumberconflict/252521>\
**Category:** Elasticsearch\
**Created:** [October 19, 2020, 9:37am UTC](https://discuss.elastic.co/t/about-translogwriter-assertnoseqnumberconflict/252521 "2020-10-19T09:37:12Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kimnwuchong](https://avatars.discourse-cdn.com/v4/letter/k/3e96dc/32.png) [@kimnwuchong](https://discuss.elastic.co/u/kimnwuchong)\
**Post date:** [October 19, 2020, 9:37am UTC](https://discuss.elastic.co/t/about-translogwriter-assertnoseqnumberconflict/252521/1 "2020-10-19T09:37:12Z")

</div>

before process assertNoSeqNumberConflict, the tranlog has already added。i think the assert is not necessary。

---

<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:** [October 19, 2020, 1:32pm UTC](https://discuss.elastic.co/t/about-translogwriter-assertnoseqnumberconflict/252521/2 "2020-10-19T13:32:10Z")

</div>

No assertions are _necessary_: they are disabled in production builds after all. That doesn't mean they aren't useful. Even an assertion which can never fail is still useful as a piece of documentation, spelling out the assumptions that the code is making, and will block any changes that violate those assumptions in future.

---

<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:** [November 16, 2020, 1:32pm UTC](https://discuss.elastic.co/t/about-translogwriter-assertnoseqnumberconflict/252521/3 "2020-11-16T13:32:15Z")

</div>

Closed on November 16, 2020, 1:32pm UTC

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