Tarantool development patches archive
 help / color / mirror / Atom feed
From: Cyrill Gorcunov via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: tml <tarantool-patches@dev.tarantool.org>
Cc: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Subject: Re: [Tarantool-patches] [PATCH] test/replication: add testcase for synchro filtering
Date: Mon, 31 May 2021 20:59:01 +0300	[thread overview]
Message-ID: <YLUj5bb7wBRDWRe8@grain> (raw)
In-Reply-To: <20210531170526.675346-1-gorcunov@gmail.com>

On Mon, May 31, 2021 at 08:05:25PM +0300, Cyrill Gorcunov wrote:
> In the test we do kind of ping-pong with promote records
> to get difference in applier_synchro_filter_tx where promote
> record reached a node with proper source instance but obsolete
> row's 'term' content.
> 
> The main idea is to reach this situation we didn't figure out
> yet which filtering strategy should be choosen.
> 
> Thus the patch is not for merging but for further investigation.
> 
> issue https://github.com/tarantool/tarantool/issues/6035
> branch gorcunov/gh-6035-applier-filter-3-notest

Force updated for more precide output
---
--
-- At this point the r1 will receive the XXX record.
--
-- XXX: decode_obsolete_rows: applier 4 (obsolete 0)
-- XXX: PROMOTE: type 31 replica_id 3 (obsolete 1) group_id 0 sync 0 lsn 1 tsn 1 flags 0x1
-- XXX: PROMOTE: type 31 replica_id 4 origin_id 3 lsn 0 term 4
--
-- XXX: decode_obsolete_rows: applier 4 (obsolete 0)
-- XXX: PROMOTE: type 31 replica_id 3 (obsolete 1) group_id 0 sync 0 lsn 2 tsn 2 flags 0x1
-- XXX: PROMOTE: type 31 replica_id 4 origin_id 3 lsn 0 term 6


      reply	other threads:[~2021-05-31 17:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-31 17:05 Cyrill Gorcunov via Tarantool-patches
2021-05-31 17:59 ` Cyrill Gorcunov via Tarantool-patches [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YLUj5bb7wBRDWRe8@grain \
    --to=tarantool-patches@dev.tarantool.org \
    --cc=gorcunov@gmail.com \
    --cc=v.shpilevoy@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH] test/replication: add testcase for synchro filtering' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox