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.

Sign up for GitHub

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

Jump to bottom

Storage node failed to restart after hard reboot of host VM #1647

Closed
vdomnich-yadro opened this issue Aug 1, 2022 · 0 comments · Fixed by #1685
Closed

Storage node failed to restart after hard reboot of host VM #1647

vdomnich-yadro opened this issue Aug 1, 2022 · 0 comments · Fixed by #1685
Assignees
@fyrchik
Labels
bug Something isn't working U3 Regular

Comments

@vdomnich-yadro
Copy link
Contributor

vdomnich-yadro commented Aug 1, 2022 •
edited
Loading

Steps to Reproduce (for bugs)

The issue does not reproduce on every run.

  1. NeoFS is hosted in cloud VM.
  2. Cloud VM was force-rebooted with cloud API.
  3. After reboot completes examine status and log of neofs-storage.

Expected Behavior

Process neofs-storage is able to start correctly.

Current Behavior

Process neofs-storage fails to start - see attached log.

Context

Possibly, the issue occurs if we are writing to bolt.db at the moment of hard reboot.

Your Environment

  • Version used:
NeoFS Storage node
Version: v0.30.0 
GoVersion: go1.17.11

  • Server setup and configuration:
    Cloud hosting. VM: 4 CPU, 8 GB RAM.

  • Operating System and version (uname -a):

Linux glagoli 5.10.0-16-amd64 #1 SMP Debian 5.10.127-1 (2022-06-30) x86_64 GNU/Linux
@fyrchik fyrchik mentioned this issue Aug 15, 2022
Merged
cthulhu-rider pushed a commit that referenced this issue Aug 16, 2022
@fyrchik @cthulhu-rider
[#1647] writecache: Open DB in sync mode
4e361e2 
Close #1647.

Initially, `Sync: false` was provided because we can already lose
objects cached in memory. However, future changes in writecache will
remove inmemory cache and speed up it via other means.

Signed-off-by: Evgenii Stratonikov <evgeniy@morphbits.ru>
@carpawell carpawell mentioned this issue Sep 14, 2022
Merged
aprasolova pushed a commit to aprasolova/neofs-node that referenced this issue Oct 19, 2022
@fyrchik @aprasolova
[nspcc-dev#1647] writecache: Open DB in sync mode
76ae5e4 
Close nspcc-dev#1647.

Initially, `Sync: false` was provided because we can already lose
objects cached in memory. However, future changes in writecache will
remove inmemory cache and speed up it via other means.

Signed-off-by: Evgenii Stratonikov <evgeniy@morphbits.ru>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fyrchik fyrchik

Labels
bug Something isn't working U3 Regular
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[#1647] writecache: Open DB in sync mode fyrchik/neofs-node
3 participants
@fyrchik @alexchetaev @vdomnich-yadro