[Gluster-devel] RPC, DHT and AFR logging errors that are expected, reduce log level?

Niels de Vos ndevos at redhat.com
Thu Sep 29 14:21:05 UTC 2016


When NFS-Ganesha does an UNLINK of a filename on an inode, it does a
follow-up check to see if the inode has been deleted or if there are
still other filenames linked (like hardlinks) to it.

Users are getting confused about the errors that are logged by RPC, DHT
and AFR. The file is missing (which is often perfectly expected from a
NFS-Ganesha point of view) and this causes a flood of messages.

From https://bugzilla.redhat.com/show_bug.cgi?id=1328581#c5 :

> If we reduce the log level for
> client-rpc-fops.c:2974:client3_3_lookup_cbk there would be the
> following entries left:
> 2x dht-helper.c:1179:dht_migration_complete_check_task
> 2x afr-read-txn.c:250:afr_read_txn
> it would reduce the logging for this non-error with 10 out of 14
> messages. We need to know from the AFR and DHT team if these messages
> are sufficient for them to identify potential issues.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://www.gluster.org/pipermail/gluster-devel/attachments/20160929/02a20bc7/attachment.sig>

More information about the Gluster-devel mailing list