Description of problem: capture portmap details in glusterd's statedump. This would be quite useful while debugging stale ports issue. Version-Release number of selected component (if applicable): mainline
REVIEW: https://review.gluster.org/16764 (glusterd: add portmap details in glusterd statedump) posted (#1) for review on master by Atin Mukherjee (amukherj)
COMMIT: https://review.gluster.org/16764 committed in master by Atin Mukherjee (amukherj) ------ commit dbdfe6c353060b7af7b4250c8d6c30ed0c35783c Author: Atin Mukherjee <amukherj> Date: Sun Feb 26 23:00:21 2017 +0530 glusterd: add portmap details in glusterd statedump glusterd statedump file doesn't have information on the ports and its associated brick details. This is quite problematic if any setup ends up with stale ports and the only way to find the issue out is to gdb into the process which is always not available. This patch attempts to fill in this gap. Change-Id: I26b4fe753d752366ddf865ca3eeae3b4d577d555 BUG: 1426948 Signed-off-by: Atin Mukherjee <amukherj> Reviewed-on: https://review.gluster.org/16764 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Prashanth Pai <ppai>
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.11.0, please open a new bug report. glusterfs-3.11.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://lists.gluster.org/pipermail/announce/2017-May/000073.html [2] https://www.gluster.org/pipermail/gluster-users/