[Bugs] [Bug 1491060] PID File handling: self-heal-deamon pid file leaves stale pid and indiscriminately kills pid when glusterd is started

[bugzilla at redhat.com]

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

Atin Mukherjee <amukherj at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |amukherj at redhat.com



--- Comment #5 from Atin Mukherjee <amukherj at redhat.com> ---
commit 220d406ad13d840e950eef001a2b36f87570058d
Author: Gaurav Kumar Garg <garg.gaurav52 at gmail.com>
Date:   Wed Mar 2 17:42:07 2016 +0530

    glusterd: Gluster should keep PID file in correct location

    Currently Gluster keeps process pid information of all the daemons
    and brick processes in Gluster configuration file directory
    (ie., /var/lib/glusterd/*).

    These pid files should be seperate from configuration files.
    Deletion of the configuration file directory might result into serious
problems.
    Also, /var/run/gluster is the default placeholder directory for pid files.

    So, with this fix Gluster will keep all process pid information of all
    processes in /var/run/gluster/* directory.

    Change-Id: Idb09e3fccb6a7355fbac1df31082637c8d7ab5b4
    BUG: 1258561
    Signed-off-by: Gaurav Kumar Garg <ggarg at redhat.com>
    Signed-off-by: Saravanakumar Arumugam <sarumuga at redhat.com>
    Reviewed-on: https://review.gluster.org/13580
    Tested-by: MOHIT AGRAWAL <moagrawa at redhat.com>
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj at redhat.com>

The above commit takes care of this issue. Please note this fix is available in
release-3.12 branch. Since this is a major change in the way pidfiles are
placed, I don't have a plan to cherry pick this into release-3.10 branch.

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