You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
main utils.c:679 E> LuajitError: .rocks/share/tarantool/vshard/storage/init.lua:3733: .rocks/share/tarantool/vshard/storage/init.lua:3595: Local replica fcbb2a69-7cab-4307-94cd-dc85699f941b wasn't found in config
Currently hot reload failes, when named identification is used.
It is cause by the fact, that we still pass uuid in storage.cfg
during reload.
Let's pass id instead of UUID. It's either uuid or name, depeding on
identification_mode. If reload is done from the old version, where no
replica.id exists, we fall back to replica.uuid.
Closestarantool#464
NO_DOC=bugfix
Currently hot reload failes, when named identification is used.
It is cause by the fact, that we still pass uuid in storage.cfg
during reload.
Let's pass id instead of UUID. It's either uuid or name, depending on
identification_mode. If reload is done from the old version, where no
replica.id exists, we fall back to replica.uuid.
Closestarantool#464
NO_DOC=bugfix
Currently hot reload failes, when named identification is used.
It is cause by the fact, that we still pass uuid in storage.cfg
during reload.
Let's pass id instead of UUID. It's either uuid or name, depending on
identification_mode. If reload is done from the old version, where no
replica.id exists, we fall back to replica.uuid.
Closes#464
NO_DOC=bugfix
Tarantool Enterprise 3.0.0-0-gf58f7d82a-r23-gc64
vshard 0.1.25
Code hot reload fails in case
identification_mode = 'name_as_key'
is used.Reproducer (no UUID):
main utils.c:679 E> LuajitError: .rocks/share/tarantool/vshard/storage/init.lua:3733: .rocks/share/tarantool/vshard/storage/init.lua:3582: Usage: cfg(configuration, this_replica_id)
Reproducer (with UUID):
The reason is likely to be this line of code
vshard/vshard/storage/init.lua
Line 4039 in bc84c65
which always uses uuid as key.
The text was updated successfully, but these errors were encountered: