From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Sat, 29 Dec 2018 15:08:49 +0300 From: Konstantin Osipov Subject: Re: [tarantool-patches] Re: [PATCH 1/5] recovery: stop writing to xstream on system error Message-ID: <20181229120849.GF17043@chai> References: <20181229090909.GD17043@chai> <20181229095052.2glj66mjb3teo73c@esperanza> <20181229105704.4oy2gn7hiyni5xvo@esperanza> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181229105704.4oy2gn7hiyni5xvo@esperanza> To: Vladimir Davydov Cc: tarantool-patches@freelists.org List-ID: * Vladimir Davydov [18/12/29 15:07]: > On Sat, Dec 29, 2018 at 12:50:52PM +0300, Vladimir Davydov wrote: > > On Sat, Dec 29, 2018 at 12:09:09PM +0300, Konstantin Osipov wrote: > > > * Vladimir Davydov [18/12/29 10:00]: > > > > > > force_recovery as an option should only affect local recovery, not > > > relays. Why is it set for relay xlog? > > > > For the record. Discussed f2f and agreed that it seems weird to set > > force_recovery for relay threads, however, changing this behavior now > > may break existing customers. So we should push this patch as is to > > 1.10, but for 2.1 do not set force_recovery flag instead. > > Here's the alternative fix that will go to 2.1: Thanks. -- Konstantin Osipov, Moscow, Russia, +7 903 626 22 32 http://tarantool.io - www.twitter.com/kostja_osipov