From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> To: sergepetrenko <sergepetrenko@tarantool.org>, georgy@tarantool.org Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH 1/5] box: update comment describing join protocol Date: Sun, 22 Dec 2019 18:58:37 +0100 [thread overview] Message-ID: <82585d68-692f-9573-5315-85297602920e@tarantool.org> (raw) In-Reply-To: <f1bf74f73e6c9095e8c3e743369f4d470581936d.1576443171.git.sergepetrenko@tarantool.org> Thanks for the patch! See 1 question below. On 15/12/2019 21:58, sergepetrenko wrote: > From: Serge Petrenko <sergepetrenko@tarantool.org> > > The comment states that relay sends the latest snapshot to replica > during initial join, however, this was changed in commit > 6332aca655ae7f95d391bdc0109e79915f6e6ad0 (relay: join new replicas off > read view). > Now relay sends rows from the read view created at the moment of join. > Update the comment to match. > > Follow-up #1271 > --- > src/box/box.cc | 7 ++++--- > 1 file changed, 4 insertions(+), 3 deletions(-) > > diff --git a/src/box/box.cc b/src/box/box.cc > index b119c927b..76fe0d534 100644 > --- a/src/box/box.cc > +++ b/src/box/box.cc > @@ -1391,13 +1391,14 @@ box_process_join(struct ev_io *io, struct xrow_header *header) > * => JOIN { INSTANCE_UUID: replica_uuid } > * <= OK { VCLOCK: start_vclock } > * Replica has enough permissions and master is ready for JOIN. > - * - start_vclock - vclock of the latest master's checkpoint. > + * - start_vclock - master's vclock at the time of join. > * > * <= INSERT > * ... > * Initial data: a stream of engine-specifc rows, e.g. snapshot > - * rows for memtx or dirty cursor data for Vinyl. Engine can > - * use REPLICA_ID, LSN and other fields for internal purposes. > + * rows for memtx or dirty cursor data for Vinyl fed from a read-view. > + * Engine can use REPLICA_ID, LSN and other fields for internal > + * purposes. Rule of 66's ship has already sailed here, but lets at least keep it in 80. Also I have a question about what are the internal purposes? I really don't know. From what I see in the next commits, purposes of REPLICA_ID and LSN didn't change in this patchset. > * ... > * <= INSERT > * <= OK { VCLOCK: stop_vclock } - end of initial JOIN stage. >
next prev parent reply other threads:[~2019-12-22 17:58 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-12-15 20:56 [Tarantool-patches] [PATCH 0/5] introduce anonymous replicas sergepetrenko 2019-12-15 20:58 ` [Tarantool-patches] [PATCH 1/5] box: update comment describing join protocol sergepetrenko 2019-12-22 17:58 ` Vladislav Shpilevoy [this message] 2019-12-23 21:12 ` Sergey Petrenko 2019-12-15 20:58 ` [Tarantool-patches] [PATCH 2/5] replication: do not decode replicaset uuid when processing a subscribe sergepetrenko 2019-12-15 20:58 ` [Tarantool-patches] [PATCH 3/5] applier: split join processing into two stages sergepetrenko 2019-12-22 17:59 ` Vladislav Shpilevoy 2019-12-23 22:10 ` Sergey Petrenko 2019-12-24 15:50 ` Vladislav Shpilevoy 2019-12-15 20:58 ` [Tarantool-patches] [PATCH 4/5] vclock: ignore 0th component in comparisons sergepetrenko 2019-12-22 17:59 ` Vladislav Shpilevoy 2019-12-23 21:26 ` Sergey Petrenko 2019-12-23 22:58 ` Sergey Petrenko 2019-12-26 4:43 ` Konstantin Osipov 2019-12-26 5:02 ` Konstantin Osipov 2019-12-27 12:56 ` Sergey Petrenko 2019-12-27 13:31 ` Konstantin Osipov 2019-12-27 13:48 ` Sergey Petrenko 2019-12-27 14:40 ` Konstantin Osipov 2019-12-15 20:58 ` [Tarantool-patches] [PATCH 5/5] replication: introduce anonymous replica sergepetrenko 2019-12-16 13:28 ` Serge Petrenko 2019-12-20 12:06 ` Serge Petrenko 2019-12-22 17:58 ` Vladislav Shpilevoy 2019-12-25 12:40 ` Sergey Petrenko 2019-12-25 18:23 ` Vladislav Shpilevoy 2019-12-26 16:08 ` Sergey Petrenko 2019-12-15 21:00 ` [Tarantool-patches] [PATCH 0/5] introduce anonymous replicas Sergey Petrenko 2019-12-18 7:49 ` Georgy Kirichenko 2019-12-20 12:07 ` Serge Petrenko 2019-12-20 12:17 ` Serge Petrenko 2019-12-22 17:59 ` Vladislav Shpilevoy
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=82585d68-692f-9573-5315-85297602920e@tarantool.org \ --to=v.shpilevoy@tarantool.org \ --cc=georgy@tarantool.org \ --cc=sergepetrenko@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 1/5] box: update comment describing join protocol' \ /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