Tarantool development patches archive
 help / color / mirror / Atom feed
From: Serge Petrenko <sergepetrenko@tarantool.org>
To: v.shpilevoy@tarantool.org, Cyrill Gorcunov <gorcunov@gmail.com>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH 0/4] make clear_synchro_queue commit everything
Date: Fri, 11 Dec 2020 12:19:56 +0300	[thread overview]
Message-ID: <696df4e5-d79a-443c-fb2b-9710aecbd928@tarantool.org> (raw)
In-Reply-To: <cover.1607633488.git.sergepetrenko@tarantool.org>


10.12.2020 23:55, Serge Petrenko пишет:
> The patchset fails `replication/election_qsync_stress.test.lua` test.
> I haven't found the reason for this yet, but I still think it may be reviewed
> while I'm trying to figure out where the test failures come from.
>
> Serge Petrenko (4):
>    box: add a single execution guard to clear_synchro_queue
>    relay: rename is_raft_enabled message to relay_is_running
>    relay: introduce relay_lsn_watcher
>    box: rework clear_synchro_queue to commit everything
>
>   src/box/box.cc                                | 143 +++++++++++++++---
>   src/box/box.h                                 |   2 +-
>   src/box/lua/ctl.c                             |   4 +-
>   src/box/relay.cc                              | 120 +++++++++++----
>   src/box/relay.h                               |  44 ++++++
>   test/replication/election_replica.lua         |   5 +-
>   ...5435-clear-synchro-queue-commit-all.result | 137 +++++++++++++++++
>   ...35-clear-synchro-queue-commit-all.test.lua |  60 ++++++++
>   test/replication/suite.cfg                    |   1 +
>   9 files changed, 460 insertions(+), 56 deletions(-)
>   create mode 100644 test/replication/gh-5435-clear-synchro-queue-commit-all.result
>   create mode 100644 test/replication/gh-5435-clear-synchro-queue-commit-all.test.lua
>

https://github.com/tarantool/tarantool/issues/5435

sp/gh-5435-new-leader-commit-all

-- 
Serge Petrenko

      parent reply	other threads:[~2020-12-11  9:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-10 20:55 Serge Petrenko
2020-12-10 20:55 ` [Tarantool-patches] [PATCH 1/4] box: add a single execution guard to clear_synchro_queue Serge Petrenko
2020-12-17 21:43   ` Vladislav Shpilevoy
2020-12-21 10:18     ` Serge Petrenko
2020-12-21 17:11       ` Vladislav Shpilevoy
2020-12-23 12:01         ` Serge Petrenko
2020-12-10 20:55 ` [Tarantool-patches] [PATCH 2/4] relay: rename is_raft_enabled message to relay_is_running Serge Petrenko
2020-12-17 21:43   ` Vladislav Shpilevoy
2020-12-23 12:01     ` Serge Petrenko
2020-12-10 20:55 ` [Tarantool-patches] [PATCH 3/4] relay: introduce relay_lsn_watcher Serge Petrenko
2020-12-17 21:43   ` Vladislav Shpilevoy
     [not found]     ` <4b7f4fc1-6d48-4332-c432-1eeb0b28c016@tarantool.org>
2020-12-23 12:03       ` Serge Petrenko
2020-12-10 20:55 ` [Tarantool-patches] [PATCH 4/4] box: rework clear_synchro_queue to commit everything Serge Petrenko
2020-12-17 21:43   ` Vladislav Shpilevoy
2020-12-23 12:04     ` Serge Petrenko
2020-12-11  7:15 ` [Tarantool-patches] [PATCH 0/4] make clear_synchro_queue " Serge Petrenko
2020-12-11  9:19 ` Serge Petrenko [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=696df4e5-d79a-443c-fb2b-9710aecbd928@tarantool.org \
    --to=sergepetrenko@tarantool.org \
    --cc=gorcunov@gmail.com \
    --cc=tarantool-patches@dev.tarantool.org \
    --cc=v.shpilevoy@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH 0/4] make clear_synchro_queue commit everything' \
    /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