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 CC6C730C25 for ; Thu, 20 Jun 2019 04:07:38 -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 oo1hW7HvAD3g for ; Thu, 20 Jun 2019 04:07:38 -0400 (EDT) Received: from smtp43.i.mail.ru (smtp43.i.mail.ru [94.100.177.103]) (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 8870730893 for ; Thu, 20 Jun 2019 04:07:38 -0400 (EDT) Received: by smtp43.i.mail.ru with esmtpa (envelope-from ) id 1hds6a-0005vq-O7 for tarantool-patches@freelists.org; Thu, 20 Jun 2019 11:07:37 +0300 Date: Thu, 20 Jun 2019 11:07:36 +0300 From: Konstantin Osipov Subject: [tarantool-patches] Re: [PATCH v4 8/9] applier: apply transaction in parallel Message-ID: <20190620080736.GI15155@atlas> References: <4226262.a1cURWbef2@home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4226262.a1cURWbef2@home.lan> 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: tarantool-patches@freelists.org * Георгий Кириченко [19/06/20 10:44]: > I'm sorry, there is proper version of the commit: > > Applier use asynchronous transaction to batch journal writes. All > appliers share the replicaset.applier.tx_vclock which means the vclock > applied but not necessarily written to a journal. Appliers use a trigger > to coordinate in case of failure - when a transaction is going to > be rolled back. Also an applier writer condition is shared across all > appliers and signaled in case of commit or hearth beat message. I only now figured out that you have no sequencer object. Don't you think it should be a proper object with its own state? Looks like now the sequencer state is shared across multiple objects. -- Konstantin Osipov, Moscow, Russia