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: [Tarantool-patches] [PATCH 0/3] box/info: report replication.X.downstream.lag Date: Thu, 21 Jan 2021 20:17:49 +0300 [thread overview] Message-ID: <20210121171753.186891-1-gorcunov@gmail.com> (raw) In the series we add reporting replication.X.downstream.lag value to complement replication.X.upstream.lag. Note that this value represent exact counter part of upstream.lag since detailed statistics about qsync and synchronous acks has a different meaning and gonna be implemented in #5191. Please take a look once time permit. As far as I can tell we can safely start encoding timestamp into vclock message without affecting any old instances. I've grepped the 1.10.x series for potential problems and didn't find any sign of. issue https://github.com/tarantool/tarantool/issues/5447 branch gorcunov/gh-5447-relay-lag Cyrill Gorcunov (3): xrow: encode timestamp into vclock message box/info: report replication.X.downstream.lag value test: replication/status -- fetch downstream lag field src/box/lua/info.c | 9 ++++++++- src/box/relay.cc | 17 +++++++++++++++++ src/box/relay.h | 8 ++++++++ src/box/xrow.c | 1 + test/replication/status.result | 8 ++++++++ test/replication/status.test.lua | 6 ++++++ 6 files changed, 48 insertions(+), 1 deletion(-) base-commit: fc86213cd7cda0641df95b1a81949bab85c19fce -- 2.29.2
next reply other threads:[~2021-01-21 17:18 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-21 17:17 Cyrill Gorcunov via Tarantool-patches [this message] 2021-01-21 17:17 ` [Tarantool-patches] [PATCH 1/3] xrow: encode timestamp into vclock message Cyrill Gorcunov via Tarantool-patches 2021-01-31 17:43 ` Vladislav Shpilevoy via Tarantool-patches 2021-01-21 17:17 ` [Tarantool-patches] [PATCH 2/3] box/info: report replication.X.downstream.lag value Cyrill Gorcunov via Tarantool-patches 2021-01-27 11:56 ` Serge Petrenko via Tarantool-patches 2021-01-27 12:12 ` Cyrill Gorcunov via Tarantool-patches 2021-01-27 14:04 ` Serge Petrenko via Tarantool-patches 2021-01-27 14:38 ` Cyrill Gorcunov via Tarantool-patches 2021-01-27 14:44 ` Serge Petrenko via Tarantool-patches 2021-01-31 17:45 ` Vladislav Shpilevoy via Tarantool-patches 2021-01-21 17:17 ` [Tarantool-patches] [PATCH 3/3] test: replication/status -- fetch downstream lag field Cyrill Gorcunov via Tarantool-patches 2021-01-31 17:46 ` Vladislav Shpilevoy via Tarantool-patches 2021-01-21 17:17 ` Cyrill Gorcunov via Tarantool-patches 2021-01-21 17:23 ` Cyrill Gorcunov via Tarantool-patches
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=20210121171753.186891-1-gorcunov@gmail.com \ --to=tarantool-patches@dev.tarantool.org \ --cc=gorcunov@gmail.com \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 0/3] box/info: report replication.X.downstream.lag' \ /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