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

[leo_storage]500 error can occur under heavy load with N=1 #401

Closed
mocchira opened this issue Jul 16, 2015 · 4 comments
Closed

[leo_storage]500 error can occur under heavy load with N=1 #401

mocchira opened this issue Jul 16, 2015 · 4 comments

Comments

@mocchira
Copy link
Member

When R:W = 8:2 benchmarking on all-in-one env with N=1,
500 errors can occur due to failing the read repair process.

@yosukehara
Copy link
Member

@mocchira Thanks for your report. I'll implement that leo_storage does not execute read-repair in case of N=1.

yosukehara added a commit to leo-project/leo_storage that referenced this issue Jul 16, 2015
yosukehara added a commit to leo-project/leo_storage that referenced this issue Jul 16, 2015
@yosukehara
Copy link
Member

I've fixed this issue, which will be included in LeoFS v1.4.0-pre1.

yosukehara added a commit to leo-project/leo_storage that referenced this issue Jul 16, 2015
@mocchira
Copy link
Member Author

Confirm Degrade

@mocchira mocchira reopened this Jul 17, 2015
@mocchira
Copy link
Member Author

As get_fun return {ok, #metadata{}, #object{}} in normal case,
We need to convert it to {ok, #metadata, Binary}.

mocchira added a commit to leo-project/leo_storage that referenced this issue Jul 17, 2015
mocchira added a commit to leo-project/leo_storage that referenced this issue Jul 17, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants