Red Hat Bugzilla – Bug 1020183
Improve the logging within the plugin so that it is easier to debug
Last modified: 2017-01-26 21:56:59 EST
Description of problem:
Actual version of shim (now 2.1.4) logs only few lines about shim version and no other (debugging) information and records. It would be good to have possibility to get more information about running actions.
One example is debugging problem with getfattr (see bug 1002020) - executed Hadoop (mapreduce) job fails with general "Cannot get layout" exception and it is not clear what is the problem.
> It happens when xtended attrs arent available either:
> 1) Because user running task or job doesnt have sudo privileges and your hadoop config (core-site.xml) sets the getfattr command to use sudo.
> 2) Your gluster mount is severely broken, or not mounted at all.
> 3) You are running without a TTY (i.e. this happens when jenkins launches our jobs - even if it is root - so you have to disable tty in sudoers - yes even for root!)
> 4) If /usr/bin/getfattr isnt installed (in a fedora19 distro, i found i had to manually install it: yum install yum install attr)
Version-Release number of selected component (if applicable):
Agreed that we (1) need a revised logging patch + (2) instructions on the
forge.gluster.org about how to debug the shim and capture/ configure logs.
Per 11/13 bug triage meeting, re-assigning to bchilds and mark medium.