From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: Alexander Turenko <alexander.turenko@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH] net.box: fix fetching of schema of an old version
Date: Sat, 4 Apr 2020 00:53:53 +0200 [thread overview]
Message-ID: <78056845-c72f-f97e-de62-2f04baaed0e0@tarantool.org> (raw)
In-Reply-To: <65798b71932c21183072decd2cce8b2b0f88b884.1585773275.git.alexander.turenko@tarantool.org>
Hi! Thanks for the patch!
On 01/04/2020 22:45, Alexander Turenko wrote:
> After 2.2.0-633-gaa0964ae1 ('net.box: fix schema fetching from 1.10/2.1
> servers') net.box expects that _vcollation system view exists on a
> tarantool server of 2.2.1+ version. This is however not always so: a
> server may be run on a new version of tarantool, but work on a schema of
> an old version.
>
> The situation with non last schema is usual for replication cluster in
> process of upgrading: all instances run on the new version of tarantool
> first (no auto-upgrade is performed by tarantools in a cluster). Then
> box.schema.upgrade() should be called, but the instances should be
> operable even before the call.
>
> Before the commit net.box was unable to connect a server if it is run on
> a schema without _vcollation system view (say, 2.1.3), but the server
> executable is of 2.2.1 version or newer.
>
> Follows up #4307
> Fixes #4691
> ---
>
> https://github.com/tarantool/tarantool/issues/4691
> https://github.com/tarantool/tarantool/tree/Totktonada/gh-4691-net-box-connect-schema-2-1-3
>
> src/box/lua/net_box.lua | 9 ++
> ...4691-net-box-connect-schema-2-1-3.test.lua | 93 ++++++++++++++++++
> test/box-tap/no_auto_schema_upgrade.lua | 30 ++++++
> .../snap/2.1.3/00000000000000000000.snap | Bin 0 -> 4466 bytes
> 4 files changed, 132 insertions(+)
> create mode 100755 test/box-tap/gh-4691-net-box-connect-schema-2-1-3.test.lua
We have xlog/upgrade suite specifically for these tests. With
already designed processes, where and how to store old snaps, etc.
See xlog/upgrade/how_to_add_new_test.md.
next prev parent reply other threads:[~2020-04-03 22:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 20:45 Alexander Turenko
2020-04-02 21:20 ` Alexander Turenko
2020-04-03 22:53 ` Vladislav Shpilevoy [this message]
2020-04-03 23:38 ` Alexander Turenko
2020-04-04 17:40 ` Vladislav Shpilevoy
2020-04-05 12:05 ` Alexander Turenko
2020-04-05 16:41 ` Vladislav Shpilevoy
2020-04-06 11:39 ` Alexander Turenko
2020-04-09 21:30 ` Vladislav Shpilevoy
2020-04-19 16:23 ` Alexander Turenko
2020-04-19 17:02 ` Vladislav Shpilevoy
2020-04-19 16:22 ` Alexander Turenko
2020-04-19 17:02 ` Vladislav Shpilevoy
2020-04-20 6:58 ` Alexander Turenko
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=78056845-c72f-f97e-de62-2f04baaed0e0@tarantool.org \
--to=v.shpilevoy@tarantool.org \
--cc=alexander.turenko@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH] net.box: fix fetching of schema of an old version' \
/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