Bug 1599808
Summary: | Change default logrotate settings in RHGS | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Sahina Bose <sabose> |
Component: | glusterfs | Assignee: | Amar Tumballi <atumball> |
Status: | CLOSED ERRATA | QA Contact: | Bala Konda Reddy M <bmekala> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | rhgs-3.3 | CC: | akrishna, asriram, atumball, ekuric, kiyer, rhs-bugs, sanandpa, sankarshan, sasundar, sheggodu, vbellur |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | RHGS 3.4.z Batch Update 2 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.12.2-27 | Doc Type: | Enhancement |
Doc Text: |
With this update, gluster logrotate config considers the size of the log file, so that gluster logs does not grow to consume all the storage. Hence, the gluster log file size will be predictable.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-12-17 17:07:02 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
Sahina Bose
2018-07-10 15:48:12 UTC
upstream patch: https://review.gluster.org/21187 This can be fixed as a separate 'installation' patch in RHHI.. or as a Batch Update, if critical. Unless marked blocker, this may not make it to downstream yet. *** Bug 1466455 has been marked as a duplicate of this bug. *** Updated the doc text. kindly review for technical Accuracy. What is the version of "logrotate --version" Also note that, the execution of logrotate is as per crontab or other setup, and it should be invoked by a setup. I suspect because of the option 'weekly', it is setup to check once in a week. We need to see if adding logrotate script to hourly makes any difference. 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-2018:3827 |