[Gluster-users] GlusterFS logging

Philippe Muller philippe.muller at gmail.com
Fri Jun 22 13:22:41 UTC 2012

Hi Amar,

# gluster volume set help | grep log
Option: diagnostics.brick-log-level
Description: Changes the log-level of the bricks
Option: diagnostics.client-log-level
Description: Changes the log-level of the clients
Option: diagnostics.brick-sys-log-level
Description: Gluster's syslog log-level
Option: diagnostics.client-sys-log-level
Description: Gluster's syslog log-level
Description: On an UNSTABLE write from client, return STABLE flag to force
client to not send a COMMIT request. In some environments, combined with a
replicated GlusterFS setup, this option can improve write performance. This
flag allows user to trust Gluster replication logic to sync data to the
disks and recover when required. COMMIT requests if received will be
handled in a default manner by fsyncing. STABLE writes are still handled in
a sync manner. Off by default.

On Fri, Jun 22, 2012 at 2:41 PM, Amar Tumballi <amarts at redhat.com> wrote:

> On 06/20/2012 04:18 PM, Philippe Muller wrote:
>> Hi GlusterFS users,
>> I'm looking for the proper way to manage GlusterFS 3.3 logs.
>> First, I'd like to centralize all logs coming from GlusterFS. I read
>> posts mentioning syslog support in this mailing-list archives. I tried a
>> few volume options like "sys-log-level" or
>> "[client|brick].syslog-level", but the gluster cli command says these
>> options doesn't exist.
> Can you try "gluster volume set help | grep log" ??
> Regards,
> Amar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20120622/8b41aaf9/attachment.html>

More information about the Gluster-users mailing list