From: Yaroslav Dynnikov <yaroslav.dynnikov@tarantool.org>
To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Cc: yaroslav.dynnikov@tarantool.org, tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH vshard 1/2] storage: introduce upgrade strategy
Date: Tue, 24 Mar 2020 18:21:32 +0300 [thread overview]
Message-ID: <CAK0MaD2+++TtLgChoMQGmFEB9m0nsv4YJ8Wjebbz4g+cfS1BWA@mail.gmail.com> (raw)
In-Reply-To: <364ea64d7bf6beef8cea83ff2fbb432ba967cd80.1584817081.git.v.shpilevoy@tarantool.org>
[-- Attachment #1: Type: text/plain, Size: 1974 bytes --]
Hi, Vlad.
I've run my cartridge upgrade tests on your branch (6e50e26c), and it's ok
on tarantool 2.2, but fails for 1.10:
```
replica | ApplyConfigError: Space _schema does not support multi-statement
transactions
replica | stack traceback:
replica | ...cartridge/.rocks/share/tarantool/vshard/storage/init.lua:419:
in function 'schema_upgrade'
replica | ...cartridge/.rocks/share/tarantool/vshard/storage/init.lua:2336:
in function 'cfg'
```
Here are results from Gitlab CI:
https://gitlab.com/tarantool/cartridge/pipelines/129256300
And here is one more remark about the patch itself.
On Sat, 21 Mar 2020 at 21:59, Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
wrote:
>
> local function this_is_master()
> @@ -2169,8 +2276,12 @@ local function storage_cfg(cfg, this_replica_uuid,
> is_reload)
> error(err)
> end
> log.info("Box has been configured")
> - local uri = luri.parse(this_replica.uri)
> - box.once("vshard:storage:1", storage_schema_v1, uri.login,
> uri.password)
> + end
> +
> + local uri = luri.parse(this_replica.uri)
> + schema_upgrade(is_master, uri.login, uri.password)
> +
> + if not is_reload then
>
It seems like this `if/else` statement isn't necessary. The `else` branch
is enough for both cases.
Even it's not hot reload it would result in `local old = nil;
box.space._bucket:on_replace(new_trigger, nil)` which is essentially the
same
> box.space._bucket:on_replace(bucket_generation_increment)
> else
> local old = box.space._bucket:on_replace()[1]
> @@ -2469,6 +2580,8 @@ M.rlist = {
> add_tail = rlist_add_tail,
> remove = rlist_remove,
> }
> +M.schema_latest_version = schema_latest_version
> +M.schema_current_version = schema_current_version
>
> return {
> sync = sync,
> --
> 2.21.1 (Apple Git-122.3)
>
>
--
С уважением.
Дынников Ярослав.
[-- Attachment #2: Type: text/html, Size: 3976 bytes --]
next prev parent reply other threads:[~2020-03-24 15:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 18:59 [Tarantool-patches] [PATCH vshard 0/2] vshard upgrade and _call Vladislav Shpilevoy
2020-03-21 18:59 ` [Tarantool-patches] [PATCH vshard 1/2] storage: introduce upgrade strategy Vladislav Shpilevoy
2020-03-22 5:05 ` Oleg Babin
2020-03-22 19:12 ` Vladislav Shpilevoy
2020-03-23 6:35 ` Oleg Babin
2020-03-23 22:32 ` Vladislav Shpilevoy
2020-03-24 4:32 ` Oleg Babin
2020-03-24 15:21 ` Yaroslav Dynnikov [this message]
2020-03-24 23:44 ` Vladislav Shpilevoy
2020-03-21 18:59 ` [Tarantool-patches] [PATCH vshard 2/2] storage: introduce vshard.storage._call() Vladislav Shpilevoy
2020-03-22 5:08 ` Oleg Babin
2020-03-22 19:13 ` Vladislav Shpilevoy
2020-03-23 6:42 ` Oleg Babin
2020-03-23 22:32 ` 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=CAK0MaD2+++TtLgChoMQGmFEB9m0nsv4YJ8Wjebbz4g+cfS1BWA@mail.gmail.com \
--to=yaroslav.dynnikov@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--cc=v.shpilevoy@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH vshard 1/2] storage: introduce upgrade strategy' \
/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