Show Table of Contents
15.5. Suppressing Repetitive Log Messages
Repetitive log messages in the Red Hat Storage Server can be configured by setting a
log-flush-timeout period and by defining a log-buf-size buffer size options with the gluster volume set command.
Suppressing Repetitive Log Messages with a Timeout Period
To set the timeout period on the bricks:
# gluster volume set VOLNAME diagnostics.brick-log-flush-timeout <value>
Example 15.13. Set a timeout period on the bricks
# gluster volume set testvol diagnostics.brick-log-flush-timeout 200 volume set: success
To set the timeout period on the clients:
# gluster volume set VOLNAME diagnostics.client-log-flush-timeout <value>
Example 15.14. Set a timeout period on the clients
# gluster volume set testvol diagnostics.client-log-flush-timeout 180 volume set: success
To set the timeout period on
glusterd:
# glusterd --log-flush-timeout=<value>
Example 15.15. Set a timeout period on the glusterd
# glusterd --log-flush-timeout=60
Suppressing Repetitive Log Messages by defining a Buffer Size
The maximum number of unique log messages that can be suppressed until the timeout or buffer overflow, whichever occurs first on the bricks.
To set the buffer size on the bricks:
# gluster volume set VOLNAME diagnostics.brick-log-buf-size <value>
Example 15.16. Set a buffer size on the bricks
# gluster volume set testvol diagnostics.brick-log-buf-size 10 volume set: success
To set the buffer size on the clients:
# gluster volume set VOLNAME diagnostics.client-log-buf-size <value>
Example 15.17. Set a buffer size on the clients
# gluster volume set testvol diagnostics.client-log-buf-size 15 volume set: success
To set the log buffer size on
glusterd:
# glusterd --log-buf-size=<value>
Example 15.18. Set a log buffer size on the glusterd
# glusterd --log-buf-size=10
Note
To disable suppression of repetitive log messages, set the log-buf-size to zero.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.