From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp48.i.mail.ru (smtp48.i.mail.ru [94.100.177.108]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id 0C23A45C304 for ; Tue, 1 Dec 2020 11:46:41 +0300 (MSK) References: <20201130093551.62113-1-sergepetrenko@tarantool.org> <02a31724-3374-287e-b4b8-6ddd7134320b@tarantool.org> From: Serge Petrenko Message-ID: <0393f979-091a-b25d-0e09-b4171320329f@tarantool.org> Date: Tue, 1 Dec 2020 11:46:40 +0300 MIME-Version: 1.0 In-Reply-To: <02a31724-3374-287e-b4b8-6ddd7134320b@tarantool.org> Content-Type: text/plain; charset="utf-8"; format="flowed" Content-Transfer-Encoding: 8bit Content-Language: en-GB Subject: Re: [Tarantool-patches] [PATCH v2] box: make instace ro while limbo is not empty List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vladislav Shpilevoy , gorcunov@gmail.com, "Alexander V. Tikhonov" Cc: tarantool-patches@dev.tarantool.org 01.12.2020 00:22, Vladislav Shpilevoy пишет: > Hi! Thanks for the patch! > > On 30.11.2020 10:35, Serge Petrenko via Tarantool-patches wrote: >> Users usually use box.ctl.wait_rw() to determine the moment when the >> instance becomes writeable. >> Since the synchronous replication introduction, this function became >> pointless, because even when an instance is writeable, it may fail at >> writing something because its limbo is not empty. >> To fix the problem introduce a new helper, txn_limbo_is_ro() and start >> using it in box_update_ro_summary(). >> Call bax_update_ro_summary() every time the limbo gets emptied out or > bax -> box. Thanks! Fixed. > >> changes an owner. >> >> Closes #5440 > Sasha (Tikh.), please, validate the branch is good to push. -- Serge Petrenko