From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 177A2316DA for ; Fri, 21 Jun 2019 15:48:46 -0400 (EDT) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p_lPJVh09pzT for ; Fri, 21 Jun 2019 15:48:46 -0400 (EDT) Received: from smtp39.i.mail.ru (smtp39.i.mail.ru [94.100.177.99]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTPS id C6EB7316CF for ; Fri, 21 Jun 2019 15:48:45 -0400 (EDT) Date: Fri, 21 Jun 2019 22:48:43 +0300 From: Konstantin Osipov Subject: [tarantool-patches] Re: [PATCH 2/2] swim: introduce generation Message-ID: <20190621194843.GB28557@atlas> References: <9852675764d25bdc720023ed6763d97cbeab8bee.1561065646.git.v.shpilevoy@tarantool.org> <20190621065358.GF18958@atlas> <9a45ac3e-0bf7-6aad-e673-494c1e20a8da@tarantool.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9a45ac3e-0bf7-6aad-e673-494c1e20a8da@tarantool.org> Sender: tarantool-patches-bounce@freelists.org Errors-to: tarantool-patches-bounce@freelists.org Reply-To: tarantool-patches@freelists.org List-Help: List-Unsubscribe: List-software: Ecartis version 1.0.0 List-Id: tarantool-patches List-Subscribe: List-Owner: List-post: List-Archive: To: Vladislav Shpilevoy Cc: tarantool-patches@freelists.org * Vladislav Shpilevoy [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