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

[#38] Update versions #39

Merged
merged 3 commits into from
Nov 14, 2022
Merged

Conversation

masterSplinter01
Copy link
Contributor

Closes #38

Signed-off-by: Angira Kekteeva <[email protected]>
@alexvanin
Copy link
Contributor

Can you try to update chain dump with latest neofs-contract release? https://github.com/nspcc-dev/neofs-contract/releases/tag/v0.16.0

@KirillovDenis
Copy link
Contributor

This command from readme doesn't work anymore. We should update docs

@masterSplinter01
Copy link
Contributor Author

Couldn't update chain dump because it seems like nns in latest neofs-contract is broken. Going to update this later as part of the issue #41.

README.md Outdated Show resolved Hide resolved
KirillovDenis
KirillovDenis previously approved these changes Nov 9, 2022
sn/config.yaml Outdated
perm: 0660
opened_cache_capacity: 32
depth: 1
depth: 2
Copy link
Contributor

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?

Copy link
Contributor Author

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"}

Copy link
Contributor

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.

Copy link
Contributor Author

@masterSplinter01 masterSplinter01 Nov 11, 2022

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.

Copy link
Contributor

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
Copy link
Contributor

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.

Copy link
Contributor

@KirillovDenis KirillovDenis left a comment

Choose a reason for hiding this comment

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

LGTM

@alexvanin alexvanin merged commit b179495 into nspcc-dev:master Nov 14, 2022
@masterSplinter01 masterSplinter01 deleted the update_versions branch November 16, 2022 14:16
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.

Update s3 and http gateway up to v0.25.0
4 participants