From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <vdavydov.dev@gmail.com>
Date: Tue, 27 Aug 2019 21:50:41 +0300
From: Vladimir Davydov <vdavydov.dev@gmail.com>
Subject: Re: [tarantool-patches] [PATCH] replication: do not abort
 replication on ER_UNKNOWN_REPLICA
Message-ID: <20190827185041.GQ13834@esperanza>
References: <20190827160720.10494-1-kostja@tarantool.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20190827160720.10494-1-kostja@tarantool.org>
To: Konstantin Osipov <kostja@tarantool.org>
Cc: tarantool-patches@freelists.org, Konstantin Osipov <kostja.osipov@gmail.com>
List-ID: <tarantool-patches.dev.tarantool.org>

On Tue, Aug 27, 2019 at 07:07:20PM +0300, Konstantin Osipov wrote:
> From: Konstantin Osipov <kostja.osipov@gmail.com>
> 
> In 3-node replica-set, registering with the leader node
> does not guarantee the registration record arrives to the second
> peer immediately. The joining node may bootstrap faster than
> the registration record arrives to the second peer, in which
> case replication will fail to create a full mesh.

Makes sense. Ack.

> 
> Fixes gh-4455
> ---
>  src/box/applier.cc | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/src/box/applier.cc b/src/box/applier.cc
> index 4304ff055..6239fcfd3 100644
> --- a/src/box/applier.cc
> +++ b/src/box/applier.cc
> @@ -100,6 +100,7 @@ applier_log_error(struct applier *applier, struct error *e)
>  	case ER_ACCESS_DENIED:
>  	case ER_NO_SUCH_USER:
>  	case ER_SYSTEM:
> +	case ER_UNKNOWN_REPLICA:
>  		say_info("will retry every %.2lf second",
>  			 replication_reconnect_interval());
>  		break;