You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@distributedlog.apache.org by "john.lonergan" <jo...@gmail.com> on 2016/09/20 17:37:57 UTC

Duplicate transaction ids

Docs say the txn Id is  an application supplied sequence number. It is required to be non-decreasing. Users usually use either timestamp or offset.
What are  the consequences of publishing two consecutive messages with the same txn ids.

Re: Duplicate transaction ids

Posted by Leigh Stewart <ls...@twitter.com.INVALID>.

It simply must be non-decreasing- dup ids are ok.

Since txid is used for positioning, if you had a long series of identical
txids you might have to scan through a lot of records to find the record
you were really looking for if you were doing a lookup. Other than that
there should be no impact.

Thx

On Tue, Sep 20, 2016 at 10:37 AM, john.lonergan <jo...@gmail.com>
wrote:

> Docs say the txn Id is  an application supplied sequence number. It is
> required to be non-decreasing. Users usually use either timestamp or offset.
> What are  the consequences of publishing two consecutive messages with the
> same txn ids.
>