Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

storage: fix hot reload with named identification #466

Merged
merged 1 commit into from
Jan 10, 2024

Conversation

Serpentian
Copy link
Contributor

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.

Closes #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 tarantool#464

NO_DOC=bugfix
Copy link
Collaborator

@Gerold103 Gerold103 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the patch!

@Gerold103 Gerold103 merged commit ac8f82b into tarantool:master Jan 10, 2024
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Hot reload is broken if name is key
2 participants