Bug 1087198
Summary: | Quota: Soft limit crosed alert not logged in brick or syslogs | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | vpshastry <vshastry> |
Component: | quota | Assignee: | Nagaprasad Sathyanarayana <nsathyan> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | mainline | CC: | bugs, dpati, gluster-bugs, nsathyan, rgowdapp, sabose, smohan |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.6.0beta1 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 1085254 | Environment: | |
Last Closed: | 2014-11-11 08:29:56 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: | 1085254 | ||
Bug Blocks: |
Description
vpshastry
2014-04-14 06:23:30 UTC
REVIEW: http://review.gluster.org/7451 (feature/quota: Logging corrections) posted (#2) for review on master by Varun Shastry (vshastry) REVIEW: http://review.gluster.org/7451 (feature/quota: Logging corrections) posted (#3) for review on master by Varun Shastry (vshastry) REVIEW: http://review.gluster.org/7451 (feature/quota: Logging corrections) posted (#4) for review on master by Varun Shastry (vshastry) The problem is that the updation of volume wide quota size happens only after soft-timeout/hard-timeout. Quota doesn't have the updated knowledge of the quota size until the cache is updated after the timeouts leading to not log. So, setting the timeouts to 0 makes quota keeps itself updated. gluster volume quota <volname> hard-timeout 0 gluster volume quota <volname> soft-timeout 0 gluster volume quota <volname> alert-time 0 <or-a-very-minimal-value-in-the-order-of-seconds> COMMIT: http://review.gluster.org/7451 committed in master by Vijay Bellur (vbellur) ------ commit b00ef83d2b15594526b1c58ef944a7edaa7e9dfe Author: Varun Shastry <vshastry> Date: Fri Apr 11 17:31:32 2014 +0530 feature/quota: Logging corrections This patch solves the inconsistent quota usage logging when soft limit reached. Change-Id: I47e7f1e65ed4b8306a999a20cc8f6b1772d47627 BUG: 1087198 Signed-off-by: Varun Shastry <vshastry> Reviewed-on: http://review.gluster.org/7451 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur> A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED. Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html [2] http://supercolony.gluster.org/pipermail/gluster-users/ This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.6.1, please reopen this bug report. glusterfs-3.6.1 has been announced [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html [2] http://supercolony.gluster.org/mailman/listinfo/gluster-users |