-
Notifications
You must be signed in to change notification settings - Fork 9
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
[#38] Update versions #39
Conversation
Signed-off-by: Angira Kekteeva <[email protected]>
Can you try to update chain dump with latest neofs-contract release? https://github.com/nspcc-dev/neofs-contract/releases/tag/v0.16.0 |
This command from readme doesn't work anymore. We should update docs |
Couldn't update chain dump because it seems like |
9fd8465
to
a35dd27
Compare
sn/config.yaml
Outdated
perm: 0660 | ||
opened_cache_capacity: 32 | ||
depth: 1 | ||
depth: 2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we need this change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because neofs-node v.0.34.0
requires 2 components in blobstor, otherwise it raises an error:
blobstor section must have 2 components, got: 1
And configuration with 2 components and depth 1 leads to the following error:
error engine/control.go:81 shard initialization failure, skipping {"id": "MQhwV2e4rzPkFu3S8XxsSs", "error": "could not initialize *blobstor.BlobStor: failure on blobovnicza initialization stage: could not open blobovnicza 0/0: open /data/blob/blobovnicza/0/0: is a directory"}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The error reveals a bug in blobstor or your previous configuration had another depth|width. Changing the config value in source code isn't a pill.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I thought the error appeared because of increasing a number of components.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's mention in docs about volume cleaning before update and keep depth:1 width:1 parameters.
sn/config.yaml
Outdated
@@ -39,18 +39,21 @@ storage: | |||
shard_num: 1 | |||
shard: | |||
0: | |||
resync_metabase: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we need this change? It will be redunant when metabase is OK.
Signed-off-by: Angira Kekteeva <[email protected]>
Signed-off-by: Angira Kekteeva <[email protected]>
0ff2606
to
8d00670
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Closes #38