From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <vdavydov.dev@gmail.com>
Date: Sat, 29 Dec 2018 12:50:52 +0300
From: Vladimir Davydov <vdavydov.dev@gmail.com>
Subject: Re: [tarantool-patches] Re: [PATCH 1/5] recovery: stop writing to
 xstream on system error
Message-ID: <20181229095052.2glj66mjb3teo73c@esperanza>
References: <cover.1546030880.git.vdavydov.dev@gmail.com>
 <dc22e4cc81ce87fc0d852dafa96464f135bebe0a.1546030880.git.vdavydov.dev@gmail.com>
 <20181229090909.GD17043@chai>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20181229090909.GD17043@chai>
To: Konstantin Osipov <kostja@tarantool.org>
Cc: tarantool-patches@freelists.org
List-ID: <tarantool-patches.dev.tarantool.org>

On Sat, Dec 29, 2018 at 12:09:09PM +0300, Konstantin Osipov wrote:
> * Vladimir Davydov <vdavydov.dev@gmail.com> [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.