Bug 1663557
Summary: | RFE: systemd should restart glusterd on crash | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | John Strunk <jstrunk> | |
Component: | glusterd | Assignee: | Srijan Sivakumar <ssivakum> | |
Status: | CLOSED ERRATA | QA Contact: | milind <mwaykole> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | rhgs-3.4 | CC: | dwalveka, mchangir, pasik, pprakash, puebele, rhs-bugs, rkothiya, sheggodu, ssivakum, storage-qa-internal | |
Target Milestone: | --- | Keywords: | Improvement, ZStream | |
Target Release: | RHGS 3.5.z Batch Update 3 | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-6.0-38 | Doc Type: | Enhancement | |
Doc Text: |
With this update, systemd restarts the glusterd service automatically with a limit of 6 times per hour when the glusterd service crashes.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1776264 (view as bug list) | Environment: | ||
Last Closed: | 2020-12-17 04:50:16 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: | 1776264 |
Description
John Strunk
2019-01-04 20:46:51 UTC
Sounds easy to implement. Any status update? Ping? upstream patch: https://review.gluster.org/#/c/glusterfs/+/23751 https://review.gluster.org/#/c/glusterfs/+/23970/ changes number of times glusterd restarts on its own after crash. We set it to with patch mentioned on comment 5 but with https://bugzilla.redhat.com/show_bug.cgi?id=1782200#c6 changing it to 6. Thanks, Sanju 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 (glusterfs bug fix and enhancement update), 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-2020:5603 |