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

Need to fix the possibility of infinite loop w/the recover-node or the rebalance feature #427

Closed
yosukehara opened this issue Oct 20, 2015 · 1 comment
Closed

Need to fix the possibility of infinite loop w/the recover-node or the rebalance feature #427

yosukehara opened this issue Oct 20, 2015 · 1 comment
Assignees
@yosukehara
Labels
Bug _leo_storage
Milestone
1.2.18

Comments

@yosukehara
Copy link
Member

I've found LeoStorage does not consume MQ's message, this situation happens under the following conditions:

  • Exists broken objects into LeoStorage object container(s)
  • Has incorrect offset of an object in a metadata
  • Not find an object because of removing it by auto-compaction during recover-node or data-rebalance
@yosukehara yosukehara self-assigned this Oct 20, 2015
@yosukehara yosukehara added this to the 1.2.18 milestone Oct 20, 2015
@yosukehara yosukehara changed the title Need to fix the Possibility of infinite loop w/the recover-node or the rebalance feature Need to fix the possibility of infinite loop w/the recover-node or the rebalance feature Oct 20, 2015
@rr-paras-patel
Copy link

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@yosukehara yosukehara

Labels
Bug _leo_storage
Projects
None yet
Milestone
1.2.18
Development

No branches or pull requests
2 participants
@yosukehara @rr-paras-patel