[Tarantool-patches] [PATCH v4 2/4] replication: hide 0-th vclock components in replication responses

[Konstantin Osipov]

* Serge Petrenko <sergepetrenko at tarantool.org> [20/03/27 18:08]:
> If an anonymous replica is promoted to a normal one and becomes
> replication master later, its vclock contains a non-empty zero
> component, tracking local changes on this replica from the time when it
> had been anonymous. No need to pollute joining instance's vclock with
> our non-empty 0 component.
> When an anonymous replica reports its status to a remote instance it
> should also hide its 0-th vclock component.
> 
> This is needed for backward compatibility with old instances, which
> don't ignore 0th vclock component coming from a remote instance by
> default.
> Also make sure that new instances ignore 0th vclock component.

If you added vclock_compare_ignore0, suggest to introduce and use 
vclock_copy_ignore0 instead of a pair vclock_copy + vclock_reset.

Where was vclock_compare_ignore0 introduced, did I miss the
patch?

-- 
Konstantin Osipov, Moscow, Russia