Support simple versioning for the metabase #1483
Assignees
Milestone
Comments
This was referenced Jun 6, 2022
aprasolova
pushed a commit
to aprasolova/neofs-node
that referenced
this issue
Oct 19, 2022
The main problem is to distinguish the case of initial initialization and update from version 0. We can't do this at `Open`, because of `resync_metabase` flag. Thus, the following approach was taken: 1. During `Open` check whether the metabase was initialized. 2. Check for the version in `Init` or write the new one if the metabase is new. 3. Update version in `Reset`. Signed-off-by: Evgenii Stratonikov <evgeniy@nspcc.ru>
aprasolova
pushed a commit
to aprasolova/neofs-node
that referenced
this issue
Oct 19, 2022
Signed-off-by: Evgenii Stratonikov <evgeniy@nspcc.ru>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Store storage version in the metabase itself.
If metabase format has changed (like in the recent case with GCMarks), node should fail to start.
The update should be done via
resync_metabaseconfig option.The text was updated successfully, but these errors were encountered: