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 0D98730263 for ; Fri, 31 May 2019 15:29:59 -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 qtZYBjVDu-gc for ; Fri, 31 May 2019 15:29:58 -0400 (EDT) Received: from smtp32.i.mail.ru (smtp32.i.mail.ru [94.100.177.92]) (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 BFA183025E for ; Fri, 31 May 2019 15:29:58 -0400 (EDT) Date: Fri, 31 May 2019 22:29:55 +0300 From: Konstantin Osipov Subject: [tarantool-patches] Re: [PATCH v2 4/8] Remove fiber from a journal_entry structure Message-ID: <20190531192955.GC6141@atlas> References: <9890ece35b9825ee78ce27bc36044020fb9d87c0.1558598679.git.georgy@tarantool.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9890ece35b9825ee78ce27bc36044020fb9d87c0.1558598679.git.georgy@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: tarantool-patches@freelists.org Cc: Georgy Kirichenko * Georgy Kirichenko [19/05/23 11:48]: > Use a trigger to handle journal entry write done event. This relaxes > friction between fiber and transaction life cycles. Sounds like having a trigger is an overkill. Wouldn't a new method in journal vtab be sufficient? Please note that I write_concern = n_replicas features are a non-goal, I am very much against tunable consistency as a concept. -- Konstantin Osipov, Moscow, Russia