-
Notifications
You must be signed in to change notification settings - Fork 10
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
Local backend is disqualified because one namespace has broken fragments #550
Comments
@wimpers this is not of type enhancement, this is of type bug because this can cripple your setup in an instant |
Some remarks:
So it's not that bad, but nonetheless I'll have a look at it in the near future |
@domsj what do you have in mind to fix/improve this? Based upon a read failure, you disqualify for writes but still happily try reads. Isn't this a bit strange? |
@wimpers that is indeed a bit strange. We could change the behaviour so that only errors on write result in disqualifying the osd for new writes |
Did the fix for #737 also fix this one? Prob not? |
no it did not also fix this one |
@domsj @toolslive is this still an issue? |
Fixed in EE version but not in OSE version. |
We saw the following error in a proxy on the OVH setup on a global proxy:
OSD 1 is in this case a local backend and is disqualified because 1 namespace did not find enough fragments. This is maybe too painful for all other namespaces, because of the following example:
In this example we have 3 local backends with a policy of 2,1,2,1.
We have namespace A and this namespace is stored on all local backends
We have namespace B and this namespace is stored on the first two backends because of a timeout in backend 3 and policy requires only 2 backends to complete.
After some time, a disk breaks on a local backend and namespace A has
Not Enough Fragments
on backend 2, so that backend is disqualified.--> At this point namespace B will also come to a halt because he needs at least 2 backends to read.
The text was updated successfully, but these errors were encountered: