Bug 1230399
Summary: | [Snapshot] Scheduled job is not processed when one of the node of shared storage volume is down | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Avra Sengupta <asengupt> |
Component: | snapshot | Assignee: | Avra Sengupta <asengupt> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.7.1 | CC: | asengupt, ashah, bugs, gluster-bugs, rjoseph, senaik |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | Scheduler | ||
Fixed In Version: | glusterfs-3.7.3 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 1218573 | Environment: | |
Last Closed: | 2015-07-30 09:49:41 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: | 1218573 | ||
Bug Blocks: | 1223205 |
Description
Avra Sengupta
2015-06-10 19:51:57 UTC
REVIEW: http://review.gluster.org/11168 (snapshot/scheduler: Reload /etc/cron.d/glusterfs_snap_cron_tasks when shared storage is available) posted (#1) for review on release-3.7 by Avra Sengupta (asengupt) REVIEW: http://review.gluster.org/11168 (snapshot/scheduler: Reload /etc/cron.d/glusterfs_snap_cron_tasks when shared storage is available) posted (#2) for review on release-3.7 by Avra Sengupta (asengupt) COMMIT: http://review.gluster.org/11168 committed in release-3.7 by Rajesh Joseph (rjoseph) ------ commit 6dd6a7157a3b8e0532b20bb5033fcd146aacc1e6 Author: Avra Sengupta <asengupt> Date: Tue Jun 9 18:00:57 2015 +0530 snapshot/scheduler: Reload /etc/cron.d/glusterfs_snap_cron_tasks when shared storage is available Backport of http://review.gluster.org/#/c/11139/ If shared storage is not accessible, create a flag in /var/run/gluster/ So that when /etc/cron.d/glusterfs_snap_cron_tasks is available again, the flag will tell us, to reload /etc/cron.d/glusterfs_snap_cron_tasks. Change-Id: I41b19f57ff0b8f7e0b820eaf592b0fdedb0a5d86 BUG: 1230399 Signed-off-by: Avra Sengupta <asengupt> Reviewed-on: http://review.gluster.org/11168 Tested-by: Gluster Build System <jenkins.com> Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Rajesh Joseph <rjoseph> Moving it to assigned, as the shared storage brick is wiped clean on node reboot. This happens bcoz shared storage brick is now present at /var/run/gluster/ss_brick, which is a tmpfs REVIEW: http://review.gluster.org/11534 (glusterd/shared_storage: Use /var/lib/glusterd/ss_brick as shared stroage's brick) posted (#1) for review on release-3.7 by Avra Sengupta (asengupt) REVIEW: http://review.gluster.org/11534 (glusterd/shared_storage: Use /var/lib/glusterd/ss_brick as shared storage's brick) posted (#2) for review on release-3.7 by Avra Sengupta (asengupt) COMMIT: http://review.gluster.org/11534 committed in release-3.7 by Rajesh Joseph (rjoseph) ------ commit 0efffcdb4eccac48d9eac26d7715ce24493ed753 Author: Avra Sengupta <asengupt> Date: Sun Jul 5 12:21:31 2015 +0530 glusterd/shared_storage: Use /var/lib/glusterd/ss_brick as shared storage's brick Backport of http://review.gluster.org/#/c/11533/ The brick path we use to create shared storage is /var/run/gluster/ss_brick. The problem with using this brick path is /var/run/gluster is a tmpfs and all the brick/shared storage data will be wiped off when the node restarts. Hence using /var/lib/glusterd/ss_brick as the brick path for shared storage volume as this brick and the shared storage volume is internally created by us (albeit on user's request), and contains only internal state data and no user data. Change-Id: I808d1aa3e204a5d2022086d23bdbfdd44a2cfb1c BUG: 1230399 Signed-off-by: Avra Sengupta <asengupt> Reviewed-on: http://review.gluster.org/11534 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Rajesh Joseph <rjoseph> 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.7.3, please open a new bug report. glusterfs-3.7.3 has been announced on the Gluster mailinglists [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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/12078 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user 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.7.3, please open a new bug report. glusterfs-3.7.3 has been announced on the Gluster mailinglists [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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/12078 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |