Bug 851962
Summary: | Geo-rep session started successfully even though one of the brick machine didn't have info about the session. | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Vijaykumar Koppad <vkoppad> | |
Component: | geo-replication | Assignee: | Venky Shankar <vshankar> | |
Status: | CLOSED ERRATA | QA Contact: | Vijaykumar Koppad <vkoppad> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 2.0 | CC: | aavati, amarts, bbandari, csaba, rhs-bugs, shaines, vbellur | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.4.0.13rhs-1 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 858472 (view as bug list) | Environment: | ||
Last Closed: | 2013-09-23 22:38:35 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: | ||||
Bug Blocks: | 850514, 858472 |
Description
Vijaykumar Koppad
2012-08-27 07:02:51 UTC
Vijaykumar, Could you please attache the logs if possible? fixed with newer geo-replication implementation. since geo-rep got revamped since this bug, now the behavior is, if it fails to write to the file, it fails at commit stage, it doesn't fail completely, in the sense it will have inconsistent data over the cluster. There is a bug for that Bug 994549 verified on glusterfs-3.4.0.17rhs-1.el6rhs.x86_64 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1262.html Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1262.html |