Bug 1500346
Summary: | [geo-rep]: Incorrect last sync "0" during hystory crawl after upgrade/stop-start | |||
---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Kotresh HR <khiremat> | |
Component: | geo-replication | Assignee: | Kotresh HR <khiremat> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
Severity: | medium | Docs Contact: | ||
Priority: | unspecified | |||
Version: | mainline | CC: | bugs, csaba, rhinduja, rhs-bugs, storage-qa-internal | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.13.0 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | 1474012 | |||
: | 1500853 (view as bug list) | Environment: | ||
Last Closed: | 2017-12-08 17:43:00 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: | 1474012 | |||
Bug Blocks: | 1500853 |
Comment 1
Kotresh HR
2017-10-10 12:33:25 UTC
REVIEW: https://review.gluster.org/18468 (geo-rep: Fix passive brick's last sync time) posted (#1) for review on master by Kotresh HR (khiremat) COMMIT: https://review.gluster.org/18468 committed in master by Kotresh HR (khiremat) ------ commit f18a47ee7e6e06c9a9a8893aef7957f23a18de53 Author: Kotresh HR <khiremat> Date: Tue Oct 10 08:25:19 2017 -0400 geo-rep: Fix passive brick's last sync time Passive brick's stime was not updated to the status file immediately after updating the brick root. As a result the last sync time was showing '0' until it finishes first crawl if passive worker becomes active after restart. Fix is to update the status file immediately after upgrading the brick root. Change-Id: I248339497303bad20b7f5a1d42ab44a1fe6bca99 BUG: 1500346 Signed-off-by: Kotresh HR <khiremat> 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.13.0, please open a new bug report. glusterfs-3.13.0 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://lists.gluster.org/pipermail/announce/2017-December/000087.html [2] https://www.gluster.org/pipermail/gluster-users/ |