-
Notifications
You must be signed in to change notification settings - Fork 155
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
storage node empty after 1.1.2 update and compaction #236
Comments
Thank you for your report. I want to know state and others of the incorrect node during the compaction as follows. We're going to reproduce and fix this issue ASAP.
Also, we've provided the recover-node command. You're able to recover the incorrect node with it. $ leofs-adm recover-node <incorrect-node> |
Hi @yosukehara,
The logs after starting the reoccur stay entirely empty. Logs of the compaction after update:
|
I've modify leo_redundant_manager of judgement of node fun, which 'true' is returned even if it detects an error of RING - leo-project/leo_redundant_manager@d467a28. Also, I'd like to know the cause of no effect of recover-node as follows:
|
H mate, https://gist.github.com/Licenser/6cea82808fccc65f3885 The manages execute without any errors so Ive not included them (logs are entirely entry). |
Thank you for sharing. Linked the related issue: /issues/237 |
We fixed this issue with v1.1.3. |
I updated three storage nodes from 1.0.1 to 1.1.2 the other day and ran a compaction afterwards, two of the nodes have the 'correct' size the third one has only a fraction of the files.
The files are properly gone (the size on the filesystem is the same as on the node)
I also haven't seen the nodes to 'repair' the broken node and repopulate it with data (N=3), is there any way to fore that?
The text was updated successfully, but these errors were encountered: