From: Konstantin Osipov <kostja@tarantool.org>
To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Cc: tarantool-patches@freelists.org
Subject: [tarantool-patches] Re: [PATCH 2/2] swim: introduce generation
Date: Fri, 21 Jun 2019 22:48:43 +0300 [thread overview]
Message-ID: <20190621194843.GB28557@atlas> (raw)
In-Reply-To: <9a45ac3e-0bf7-6aad-e673-494c1e20a8da@tarantool.org>
* Vladislav Shpilevoy <v.shpilevoy@tarantool.org> [19/06/21 22:31]:
Well, I don't know, it's bikeshed.
Your argument doesn't make sense however, age can not encompass
generation - an age is something you have within a generation.
Plus, I was thinking that the two fields together are the actual
swim incarnation, because only the two things together ensure
strict ordering, which is swim's requirement for incarnation.
As for the API, you could return a binary or text for incarnation and
thus preserve SWIM requirements.
Basically, I thought that we keep the incarnation as before, but
make it a bit complex than what swim does by default - it's part
of your original proposal of keeping both members part of 8-byte
incarnation, but without 8-byte compromise.
--
Konstantin Osipov, Moscow, Russia
next prev parent reply other threads:[~2019-06-21 19:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 21:23 [tarantool-patches] [PATCH 0/2] SWIM generation Vladislav Shpilevoy
2019-06-20 21:23 ` [tarantool-patches] [PATCH 1/2] swim: encapsulate incarnation behind 'age' Vladislav Shpilevoy
2019-06-20 21:23 ` [tarantool-patches] [PATCH 2/2] swim: introduce generation Vladislav Shpilevoy
2019-06-21 6:53 ` [tarantool-patches] " Konstantin Osipov
2019-06-21 19:03 ` Vladislav Shpilevoy
2019-06-21 19:48 ` Konstantin Osipov [this message]
2019-06-21 19:53 ` Konstantin Osipov
2019-06-21 22:00 ` Vladislav Shpilevoy
2019-06-21 22:31 ` Konstantin Osipov
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=20190621194843.GB28557@atlas \
--to=kostja@tarantool.org \
--cc=tarantool-patches@freelists.org \
--cc=v.shpilevoy@tarantool.org \
--subject='[tarantool-patches] Re: [PATCH 2/2] swim: introduce generation' \
/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