* sergepetrenko <sergepetrenko@tarantool.org> [20/02/13 09:34]:

> There is an assertion in vclock_follow `lsn > prev_lsn`, which doesn't
> fire in release builds, of course. So we better panic on an attemt to
> write a record with a duplicate or otherwise broken lsn.
>

It should be a warning in production. You can't crash production
deploy because of a server bug, and lsn inconsistency is always a
server bug.