Bug 1484460
Summary: | [RHEL7] [GSS]high latency observed in entrylk operation that cause application experiencing high latency | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Atin Mukherjee <amukherj> | |
Component: | replicate | Assignee: | Ravishankar N <ravishankar> | |
Status: | CLOSED ERRATA | QA Contact: | Nag Pavan Chilakam <nchilaka> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | rhgs-3.2 | CC: | abhishku, amukherj, asriram, asrivast, atumball, bkunal, nchilaka, pdhange, rabhat, ravishankar, rcyriac, rhinduja, rhs-bugs, rnalakka, rwheeler, storage-qa-internal, vbellur, wenshi | |
Target Milestone: | --- | Keywords: | ZStream | |
Target Release: | RHGS 3.2.0 Async | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.8.4-18.7 | Doc Type: | Bug Fix | |
Doc Text: |
When the replication process creates an entry as part of self-heal, it uses the iatt buffer to send the create operation. Previously, entries were created regardless of iatt buffer validity. This resulted in an empty file with GFID xattr of all zeroes being created when an invalid iatt buffer was sent. Checks are now included to ensure that iatt buffer content is valid before creating the entry in this situation.
|
Story Points: | --- | |
Clone Of: | 1474178 | |||
: | 1484650 (view as bug list) | Environment: | ||
Last Closed: | 2017-09-14 08:38:53 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: |
Comment 11
Bipin Kunal
2017-09-12 13:23:01 UTC
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. https://access.redhat.com/errata/RHBA-2017:2730 |