From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> To: tarantool-patches@freelists.org, Vladimir Davydov <vdavydov.dev@gmail.com>, kostja@tarantool.org Subject: Re: [tarantool-patches] [PATCH v2 4/4] Introduce replica local spaces Date: Mon, 9 Jul 2018 21:05:23 +0300 [thread overview] Message-ID: <c2f5f06e-289b-349c-01e7-6bd51f4976fe@tarantool.org> (raw) In-Reply-To: <76b274d93aaf726501cfb0f26af4915936c12592.1531150617.git.vdavydov.dev@gmail.com> On 09/07/2018 18:40, Vladimir Davydov wrote: > This patch introduces a new space option, group_id, which defines how > the space is replicated. If it is 0 (default), the space is replicated > throughout the entire cluster. If it is 1, the space is replica local, > i.e. all changes made to it are invisible to other replicas in the > cluster. Currently, no other value is permitted, but in future we will > use this option for setting up arbitrary replication groups in a > cluster. The option can only be set on space creation and cannot be > altered. > > Technically, to support this feature, we introduce a new header key, > IPROTO_GROUP_ID, which is set to the space group id for all rows > corresponding to a space, both in xlog and in snap. Relay won't send > snapshot rows whose group_id is 1. As for xlog rows, they are > transformed to IPROTO_NOP so as to promote vclock on replicas without > any actual data modification. > > The feature is currently supported for memtx spaces only, but it should > be easy to implement it for vinyl spaces as well. > > @TarantoolBot document > Title: Document new space option - group_id > Group identifier defines how the space is replicated. Currently, only > two values are permitted: 0 and 1. If space.group_id is 0, changes made > to the space are replicated throughout the entire cluster. If it is 1, > then the space is replica local, i.e. changes made to it are invisible > to other replicas in the cluster. Please, put the doc request after 'Closes'. The request must be at the very end of the commit message. > > Closes #3443 > ---
prev parent reply other threads:[~2018-07-09 18:05 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-07-09 15:40 [PATCH v2 0/4] " Vladimir Davydov 2018-07-09 15:40 ` [PATCH v2 1/4] txn: do not require space id for nop requests Vladimir Davydov 2018-07-10 18:57 ` Konstantin Osipov 2018-07-09 15:40 ` [PATCH v2 2/4] xrow: make NOP requests bodiless Vladimir Davydov 2018-07-09 15:40 ` [PATCH v2 3/4] Rename space_opts::temporary to is_temporary Vladimir Davydov 2018-07-09 15:40 ` [PATCH v2 4/4] Introduce replica local spaces Vladimir Davydov 2018-07-09 18:05 ` Vladislav Shpilevoy [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=c2f5f06e-289b-349c-01e7-6bd51f4976fe@tarantool.org \ --to=v.shpilevoy@tarantool.org \ --cc=kostja@tarantool.org \ --cc=tarantool-patches@freelists.org \ --cc=vdavydov.dev@gmail.com \ --subject='Re: [tarantool-patches] [PATCH v2 4/4] Introduce replica local spaces' \ /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