Monday, October 31, 2016

MFS/NFS Debug Logging

                                                          MFS/NFS Debug Logging

Default log level for MapR FS is Info but there will be instances when we need to get more detailed logging while troubleshooting an  issue.

Allowed Trace Levels are: 
FATAL
ERROR
WARN
INFO
DEBUG ( Very verbose )

To set loglevel to DEBUG for all modules :

      maprcli trace setlevel -level debug -port 5660 -host <Hostname>
      maprcli trace setmode -mode continuous -port 5660 -host <Hostname>

Verify all modes set to DEBUG level :
maprcli trace info           

To set back to normal:
maprcli trace setlevel -level default -port 5660 -host <Hostname>
maprcli trace setmode -mode default -port 5660 -host <Hostname>


Debug for resync module
Debug logging can be enabled for specific modules , Like for resync/replication issue we can turn on debug logging for replication module via below commands on source and destination.

maprcli trace setlevel -level DEBUG -module Replication -host $src_host
maprcli trace setlevel -level DEBUG -module Replication -host $dest_host


MapR-DB 
Similarly if debug logging needs to be enabled for troubleshooting MapR-DB issues below are modules where debug needs to be turned on.

 maprcli trace setlevel -module DB -level debug -host <Hostname>

 maprcli trace setlevel -module DBRpc -level debug -host <Hostname>



NFS
While troubleshooting NFS issue we might need to get detailed logs of when the op reached NFS and when op was served by NFS back to client to do so we can turn on DEBUG logging in NFS via below commands.

 maprcli trace setlevel -level debug -port 9998 -host `hostname -f`
 maprcli trace setmode -mode continuous -port 9998 -host `hostname -f`


No comments:

Post a Comment