Description of problem: high cpu consuming processes leaving no trace in the logs are difficult to debug Expected results: need a script to help strace processes consuming high cpu
REVIEW: https://review.gluster.org/16778 (extras/devel-tools: script to strace processes) posted (#1) for review on master by Milind Changire (mchangir)
REVIEW: https://review.gluster.org/16778 (extras/devel-tools: script to strace processes) posted (#2) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: https://review.gluster.org/16778 (extras/devel-tools: script to strace processes) posted (#3) for review on master by Milind Changire (mchangir)
REVIEW: https://review.gluster.org/16778 (extras/devel-tools: script to strace processes) posted (#4) for review on master by Amar Tumballi
COMMIT: https://review.gluster.org/16778 committed in master by "Amar Tumballi" <amarts> with a commit message- extras/devel-tools: script to strace processes Script to strace processes at high priority. Script should be run at high priority, like nice value of -19, to help get a trace of a run-away process consuming high CPU. eg. $ nice -n -19 ./strace-brick.sh glusterfsd 50 will strace glusterfsd processes for 60 seconds which are consuming a minimum of 50% CPU. Change-Id: I6374054c7342b19122a3588d982388199f955930 BUG: 1427397 Signed-off-by: Milind Changire <mchangir>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-6.0, please open a new bug report. glusterfs-6.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://lists.gluster.org/pipermail/announce/2019-March/000120.html [2] https://www.gluster.org/pipermail/gluster-users/