glusterd log file grows indefinitely; should provide logrotate config file or option to perform rotation itself
Issue
- A gluster 3.2.2 file has grown to almost X GBs.
- The gluster* packages apparently neither take advantage of the standard logrotate facility by dropping a configuration file in /etc/logrotate.d nor provide any runtime configuration option to make gluster rotate its own logs.
Environment
- Gluster 3.2.2
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.