From: Vladimir Davydov <vdavydov.dev@gmail.com>
To: Konstantin Belyavskiy <k.belyavskiy@tarantool.org>
Cc: tarantool-patches@freelists.org, georgy <georgy@tarantool.org>
Subject: Re: [tarantool-patches] Re: [PATCH] replication: fix bug with read-only replica as a bootstrap leader
Date: Wed, 18 Apr 2018 13:34:26 +0300 [thread overview]
Message-ID: <20180418103426.vkjccesutpgj2d4s@esperanza> (raw)
In-Reply-To: <20180413123846.wr5s4pnqbdsat5dg@esperanza>
On Fri, Apr 13, 2018 at 03:38:46PM +0300, Vladimir Davydov wrote:
> On Fri, Apr 13, 2018 at 02:13:34PM +0300, Konstantin Belyavskiy wrote:
> > Please take a look at newer version.
>
> When you fix something like this, please include the new version of the
> patch in the email.
>
> The patch itself looks OK to me. Posting it here for the record.
>
> > From 983b98a91dcd70a3013de373b55294a6af468e17 Mon Sep 17 00:00:00 2001
> > From: Konstantin Belyavskiy <k.belyavskiy@tarantool.org>
> > Date: Mon, 9 Apr 2018 16:32:26 +0300
> > Subject: [PATCH] replication: fix bug with read-only replica as a bootstrap
> > leader
> >
> > When bootstrapping a new cluster, each replica from replicaset can
> > be chosen as a leader, but if it is 'read-only', bootstrap will
> > failed with an error.
> > Fixed it by eliminating read-only replicas from voting by adding
> > access rights information to IPROTO_REQUEST_VOTE reply.
> >
> > Closes #3257
Pushed to 1.9.
prev parent reply other threads:[~2018-04-18 10:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 16:02 Konstantin Belyavskiy
2018-04-11 16:11 ` [tarantool-patches] " Georgy Kirichenko
2018-04-13 8:54 ` Vladimir Davydov
2018-04-13 11:13 ` [tarantool-patches] " Konstantin Belyavskiy
2018-04-13 11:15 ` Re[2]: " Konstantin Belyavskiy
2018-04-13 12:38 ` Vladimir Davydov
2018-04-18 10:34 ` Vladimir Davydov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180418103426.vkjccesutpgj2d4s@esperanza \
--to=vdavydov.dev@gmail.com \
--cc=georgy@tarantool.org \
--cc=k.belyavskiy@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='Re: [tarantool-patches] Re: [PATCH] replication: fix bug with read-only replica as a bootstrap leader' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox