Red Hat Bugzilla – Bug 1481040
ganesha.nfsd processes steadily using high CPU on 2 nodes.
Last modified: 2017-10-16 08:17:26 EDT
Created attachment 1327513 [details]
Created attachment 1327514 [details]
At-least from QE setup, since the high CPU usage seems to be from upcall polling, this particular issue shall be addressed as part of bug1485836
Yes, please install the -debuginfo rpm(s) so that the next core and backtrace will be more helpful.
(You don't need me on-line with you to do that, right?)
Ganesha does not need to be restarted after debuginfo is installed. debuginfo is just for gdb, not for ganesha itself.
Thats right Raghavendra. If we match the thread IDs (consuming CPU) in http://collab-shell.usersys.redhat.com/01909671/x-image/sh_remote_session_26092017.png against the ones in gdb stack (http://collab-shell.usersys.redhat.com/01909671/x-text/ganeshagdb.log), they are all upcall threads. That confirms our theory that upcall polling is adding up to high CPU usage even on customer environment.
This is being addressed as part of bug1485836. We need to support on glusterfs to provide APIs to be able to register for asynchronous upcalls to be sent to application. Post that those APIs need to be consumed by ganesha.
Changes needed in gluster are sent upstream for review -