Bug 1666969
Summary: | [geo-rep]: Crashes on slave nodes | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Rochelle <rallan> |
Component: | geo-replication | Assignee: | Kotresh HR <khiremat> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Rahul Hinduja <rhinduja> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | rhgs-3.4 | CC: | csaba, moagrawa, nchilaka, pasik, rhs-bugs, sasundar, sheggodu, storage-qa-internal, sunkumar |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-6.0-1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-12-17 13:25:38 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: |
Description
Rochelle
2019-01-17 06:16:56 UTC
Hi Mohit, I'm asking you as the one who dealt with https://bugzilla.redhat.com/1644164 / authored https://review.gluster.org/21305, if is it feasible that the crashes we see in Thread 1 are because of the lack of the hardening you've made in referred work? Some more explanation about "the crashes we see in Thread 1": this might be because of improper synchronization of access to inodes. Mohit's referred work introduces stronger synchronization there and that's why it might be then a suitable fix. If it's feasible, the test could be repeated with a build that has his patch backported. (If needed I can provide it.) A crash with similar stack trace can be observed in Bug 1664173. |