storage: fix hot reload with named identification #466
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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