[Bugs] [Bug 1418981] Unable to take Statedump for gfapi applications

bugzilla at redhat.com bugzilla at redhat.com
Tue Feb 14 01:53:27 UTC 2017


https://bugzilla.redhat.com/show_bug.cgi?id=1418981



--- Comment #7 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/16600 committed in release-3.10 by
Shyamsundar Ranganathan (srangana at redhat.com) 
------
commit bd9adf99a2ca53dd18332957acb465f904ecd22c
Author: Niels de Vos <ndevos at redhat.com>
Date:   Fri Jan 6 12:49:32 2017 +0100

    gfapi: add API to trigger events for debugging and troubleshooting

    Introduce glfs_sysrq() as a generic API for triggering debug and
    troubleshoot events. This interface will be used by the feature to get
    statedumps for applications using libgfapi.

    The current events that can be requested through this API are:
     - 'h'elp: log a mesage with all supported events
     - 's'tatedump: trigger a statedump for the passed glfs_t

    In future, this API can be used by a CLI to trigger statedumps from
    storage servers. At the moment it is limited to take statedumps, but it
    is extensible to set the log-level, clear caches, force reconnects and
    much more.

    > BUG: 1169302
    > Change-Id: I18858359a3957870cea5139c79efe1365a15a992
    > Original-author: Poornima G <pgurusid at redhat.com>
    > Signed-off-by: Niels de Vos <ndevos at redhat.com>
    > Reviewed-on-master: http://review.gluster.org/16414
    > Reviewed-by: Prashanth Pai <ppai at redhat.com>
    > Reviewed-by: Kaleb KEITHLEY <kkeithle at redhat.com>

    BUG: 1418981
    Change-Id: I18858359a3957870cea5139c79efe1365a15a992
    Signed-off-by: Shyam <srangana at redhat.com>
    Reviewed-on: https://review.gluster.org/16600
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos at redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list