Description of problem: glusterd' runtime state is not directly observable. During debugging users/developers need to look at the logs, gdb the process and make (complex) inferences from them. This has been the practice due to lack of observability. This bug tracks development efforts towards make glusterd' runtime more observable. Version-Release number of selected component (if applicable): How reproducible: N/A Steps to Reproduce: 1.N/A 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/8584 (glusterd: Add last successful glusterd lock backtrace) posted (#3) for review on master by Krishnan Parthasarathi (kparthas)
REVIEW: http://review.gluster.org/8584 (glusterd: Add last successful glusterd lock backtrace) posted (#4) for review on master by Krishnan Parthasarathi (kparthas)
REVIEW: http://review.gluster.org/8584 (glusterd: Add last successful glusterd lock backtrace) posted (#5) for review on master by Krishnan Parthasarathi (kparthas)
REVIEW: http://review.gluster.org/8622 (synctask: add backtrace per waiting task) posted (#1) for review on master by Krishnan Parthasarathi (kparthas)
REVIEW: http://review.gluster.org/8584 (glusterd: Add last successful glusterd lock backtrace) posted (#6) for review on master by Krishnan Parthasarathi (kparthas)
REVIEW: http://review.gluster.org/8622 (synctask: add backtrace per waiting task) posted (#2) for review on master by Krishnan Parthasarathi (kparthas)
REVIEW: http://review.gluster.org/8584 (glusterd: Add last successful glusterd lock backtrace) posted (#7) for review on master by Krishnan Parthasarathi (kparthas)
REVIEW: http://review.gluster.org/8622 (synctask: add backtrace per waiting task) posted (#3) for review on master by Krishnan Parthasarathi (kparthas)
COMMIT: http://review.gluster.org/8584 committed in master by Krishnan Parthasarathi (kparthas) ------ commit 1b53756e50cb9ad5422292d7f4e1e6fe23357222 Author: Krishnan Parthasarathi <kparthas> Date: Wed Sep 3 11:03:06 2014 +0530 glusterd: Add last successful glusterd lock backtrace Also, moved the backtrace fetching logic to a separate function. Modified the backtrace fetching logic able to work under memory pressure conditions. Change-Id: Ie38bea425a085770f41831314aeda95595177ece BUG: 1138503 Signed-off-by: Krishnan Parthasarathi <kparthas> Reviewed-on: http://review.gluster.org/8584 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Jeff Darcy <jdarcy> Reviewed-by: Atin Mukherjee <amukherj>
COMMIT: http://review.gluster.org/8622 committed in master by Vijay Bellur (vbellur) ------ commit 58f23090fc0af2d93c02da68b06e02d1263df499 Author: Krishnan Parthasarathi <kparthas> Date: Fri Sep 5 14:55:01 2014 +0530 synctask: add backtrace per waiting task The backtrace is 'saved' in a per-task buffer. This would come handy while debugging code using synctasks. Change-Id: I732b275f6d15b31f31361f5ecf2ba47cacde9b54 BUG: 1138503 Signed-off-by: Krishnan Parthasarathi <kparthas> Reviewed-on: http://review.gluster.org/8622 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Jeff Darcy <jdarcy> Reviewed-by: Atin Mukherjee <amukherj> Reviewed-by: Vijay Bellur <vbellur>
REVIEW: http://review.gluster.org/8794 (glusterd: Add last successful glusterd lock backtrace) posted (#1) for review on release-3.6 by Krishnan Parthasarathi (kparthas)
REVIEW: http://review.gluster.org/8795 (synctask: add backtrace per waiting task) posted (#1) for review on release-3.6 by Krishnan Parthasarathi (kparthas)
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-3.7.0, please open a new bug report. glusterfs-3.7.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] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user