From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-f174.google.com (mail-lj1-f174.google.com [209.85.208.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id 0F65F46970E for ; Thu, 26 Dec 2019 08:03:00 +0300 (MSK) Received: by mail-lj1-f174.google.com with SMTP id z22so19015934ljg.1 for ; Wed, 25 Dec 2019 21:03:00 -0800 (PST) Date: Thu, 26 Dec 2019 08:02:59 +0300 From: Konstantin Osipov Message-ID: <20191226050259.GD1337@atlas> References: <20191226044338.GB1337@atlas> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191226044338.GB1337@atlas> Subject: Re: [Tarantool-patches] [PATCH 4/5] vclock: ignore 0th component in comparisons. List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: sergepetrenko , georgy@tarantool.org, tarantool-patches@dev.tarantool.org * Konstantin Osipov [19/12/26 07:43]: > * sergepetrenko [19/12/16 09:47]: > > 0th vclock component will be used to count replica-local rows of an > > anonymous replica. These rows won't be replicated and different > > instances will have different values in vclock[0]. So ignore 0th > > component in comparisons. > > I don't know how this is going to work going forward. > > vclock id 0 is already reserved for snapshots/the changes > of expelled replicas. A much safer bet would be to use a new special id number, like UINT64_MAX, and not change meaning of an existing id. -- Konstantin Osipov, Moscow, Russia