From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> To: Serge Petrenko <sergepetrenko@tarantool.org>, tarantool-patches@dev.tarantool.org, gorcunov@gmail.com Subject: Re: [Tarantool-patches] [PATCH v2 08/11] raft: relay status updates to followers Date: Tue, 22 Sep 2020 00:47:53 +0200 [thread overview] Message-ID: <5d17798d-e8aa-9a33-3e13-08c66d3cf710@tarantool.org> (raw) In-Reply-To: <6ca694f2-2e84-fcf3-ca46-15e188bfdf10@tarantool.org> Consider my commit on top of your changes: ==================== [tosquash] raft: vclock should be out parameter; reduce diff Firstly I made raft_serialize_for_network() use its vclock parameter as an out parameter. Because it is Raft's deal what vclock it wants to send. It can't be dictated by the function caller. Secondly, I renamed data back to buf in xrow.c in order to reduce diff from the previous patches. diff --git a/src/box/raft.c b/src/box/raft.c index c2ef9ff39..2bf8490ea 100644 --- a/src/box/raft.c +++ b/src/box/raft.c @@ -115,8 +115,10 @@ raft_serialize_for_network(struct raft_request *req, struct vclock *vclock) * Raft does not own vclock, so it always expects it passed externally. * Vclock is sent out only by candidate instances. */ - if (req->state == RAFT_STATE_CANDIDATE) + if (req->state == RAFT_STATE_CANDIDATE) { req->vclock = vclock; + vclock_copy(vclock, &replicaset.vclock); + } } void diff --git a/src/box/xrow.c b/src/box/xrow.c index 250794a3e..da5c6ffae 100644 --- a/src/box/xrow.c +++ b/src/box/xrow.c @@ -996,26 +996,24 @@ xrow_encode_raft(struct xrow_header *row, struct region *region, row->body[0].iov_base = buf; row->group_id = GROUP_LOCAL; row->bodycnt = 1; - char *data = buf; + const char *begin = buf; - data = mp_encode_map(data, map_size); - data = mp_encode_uint(data, IPROTO_RAFT_TERM); - data = mp_encode_uint(data, r->term); + buf = mp_encode_map(buf, map_size); + buf = mp_encode_uint(buf, IPROTO_RAFT_TERM); + buf = mp_encode_uint(buf, r->term); if (r->vote != 0) { - data = mp_encode_uint(data, IPROTO_RAFT_VOTE); - data = mp_encode_uint(data, r->vote); + buf = mp_encode_uint(buf, IPROTO_RAFT_VOTE); + buf = mp_encode_uint(buf, r->vote); } if (r->state != 0) { - data = mp_encode_uint(data, IPROTO_RAFT_STATE); - data = mp_encode_uint(data, r->state); + buf = mp_encode_uint(buf, IPROTO_RAFT_STATE); + buf = mp_encode_uint(buf, r->state); } if (r->vclock != NULL) { - data = mp_encode_uint(data, IPROTO_RAFT_VCLOCK); - data = mp_encode_vclock_ignore0(data, r->vclock); + buf = mp_encode_uint(buf, IPROTO_RAFT_VCLOCK); + buf = mp_encode_vclock_ignore0(buf, r->vclock); } - - row->body[0].iov_len = data - buf ; - + row->body[0].iov_len = buf - begin; return 0; }
next prev parent reply other threads:[~2020-09-21 22:47 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-09 23:16 [Tarantool-patches] [PATCH v2 00/11] dRaft Vladislav Shpilevoy 2020-09-09 23:16 ` [Tarantool-patches] [PATCH v2 01/11] applier: store instance_id in struct applier Vladislav Shpilevoy 2020-09-14 9:38 ` Serge Petrenko 2020-09-19 15:44 ` Vladislav Shpilevoy 2020-09-21 6:23 ` Serge Petrenko 2020-09-09 23:16 ` [Tarantool-patches] [PATCH v2 10/11] raft: introduce box.info.raft Vladislav Shpilevoy 2020-09-14 9:42 ` Serge Petrenko 2020-09-09 23:16 ` [Tarantool-patches] [PATCH v2 11/11] [tosquash] raft: a swarm of minor fixes Vladislav Shpilevoy 2020-09-14 10:13 ` Serge Petrenko 2020-09-09 23:16 ` [Tarantool-patches] [PATCH v2 02/11] box: introduce summary RO flag Vladislav Shpilevoy 2020-09-09 23:16 ` [Tarantool-patches] [PATCH v2 03/11] wal: don't touch box.cfg.wal_dir more than once Vladislav Shpilevoy 2020-09-09 23:16 ` [Tarantool-patches] [PATCH v2 04/11] replication: track registered replica count Vladislav Shpilevoy 2020-09-09 23:16 ` [Tarantool-patches] [PATCH v2 05/11] [wip] box: do not register outgoing connections Vladislav Shpilevoy 2020-09-09 23:16 ` [Tarantool-patches] [PATCH v2 06/11] raft: introduce persistent raft state Vladislav Shpilevoy 2020-09-09 23:16 ` [Tarantool-patches] [PATCH v2 07/11] raft: introduce box.cfg.raft_* options Vladislav Shpilevoy 2020-09-09 23:16 ` [Tarantool-patches] [PATCH v2 08/11] raft: relay status updates to followers Vladislav Shpilevoy 2020-09-20 17:17 ` Vladislav Shpilevoy 2020-09-21 7:13 ` Serge Petrenko 2020-09-21 10:50 ` Serge Petrenko 2020-09-21 22:47 ` Vladislav Shpilevoy [this message] 2020-09-22 8:48 ` Serge Petrenko 2020-09-21 22:47 ` Vladislav Shpilevoy 2020-09-22 8:47 ` Serge Petrenko 2020-09-09 23:17 ` [Tarantool-patches] [PATCH v2 09/11] raft: introduce state machine Vladislav Shpilevoy 2020-09-19 15:49 ` Vladislav Shpilevoy 2020-09-19 15:50 ` Vladislav Shpilevoy 2020-09-21 8:20 ` Serge Petrenko 2020-09-21 8:22 ` Serge Petrenko 2020-09-21 8:34 ` Serge Petrenko 2020-09-21 22:47 ` Vladislav Shpilevoy 2020-09-22 8:49 ` Serge Petrenko 2020-09-22 22:48 ` Vladislav Shpilevoy 2020-09-23 9:59 ` Serge Petrenko 2020-09-23 20:31 ` Vladislav Shpilevoy 2020-09-24 9:34 ` Serge Petrenko 2020-09-19 15:58 ` [Tarantool-patches] [PATCH v2 12/11] dRaft Vladislav Shpilevoy 2020-09-19 15:59 ` Vladislav Shpilevoy 2020-09-21 7:24 ` Serge Petrenko 2020-09-21 22:48 ` [Tarantool-patches] [PATCH v2 12/11] raft: add tests Vladislav Shpilevoy 2020-09-30 10:56 ` [Tarantool-patches] [PATCH v2 00/11] dRaft Kirill Yukhin
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=5d17798d-e8aa-9a33-3e13-08c66d3cf710@tarantool.org \ --to=v.shpilevoy@tarantool.org \ --cc=gorcunov@gmail.com \ --cc=sergepetrenko@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v2 08/11] raft: relay status updates to followers' \ /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