Bug 848253
Summary: | quota: brick process kill allows quota limit cross | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Vidya Sakar <vinaraya> |
Component: | glusterfs | Assignee: | Bug Updates Notification Mailing List <rhs-bugs> |
Status: | CLOSED WONTFIX | QA Contact: | Saurabh <saujain> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | amarts, gluster-bugs, mzywusko, rfortier, rhinduja, saujain, shaines, vagarwal, vbellur |
Target Milestone: | --- | Keywords: | FutureFeature, ZStream |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Known Issue | |
Doc Text: |
Cause: when quota limit is set on a distributed volume, and if a brick goes down while I/O is happening, there is a chance that the effective 'quota limit' can be exceeded as distribute translator would not see the contribution from the offline brick.
Consequence: 'quota limit' gets exceeded.
Workaround (if any): use 'replication' in case one needs 100% consistency when a node goes down.
Result: When replicate is used, it would take care of single brick failure, and quota limit will be maintained as is.
|
Story Points: | --- |
Clone Of: | 821725 | Environment: | |
Last Closed: | 2013-10-21 04:47:02 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 821725 | ||
Bug Blocks: |
Description
Vidya Sakar
2012-08-15 01:48:25 UTC
Need to have an extra flag set on the directory when quota limit is reached on a directory. Extremely hard to keep the information about the lost brick for quota computation, in non-replicated setup. But we need an enhancement to handle quota limit set flag in xattr when its ~95% of limit value. That way, we will not be missing quota limit by a large margin. This issue should just be marked as Known-Issues, and be handled by setting the 'right expectation' in admin, than that of technical solution, which would make the performance crawl, and solution never satisfying for 100% user base. Keeping this bug open till we have better understanding of requirement. Per discussion with Saurabh, moving this out of u1 list as there is a design change Per discussion with the PM and QE, not to be supported. |