REVIEW: http://review.gluster.org/14649 (cluster/ec: Restrict the launch of replace brick heal) posted (#1) for review on master by Ashish Pandey (aspandey)

COMMIT: http://review.gluster.org/14649 committed in master by Jeff Darcy (jdarcy) 
------
commit eb7ba8984c5e66b57d592f9da606fbdd1133df3b
Author: Ashish Pandey <aspandey>
Date:   Mon Jun 6 10:17:54 2016 +0530

    cluster/ec: Restrict the launch of replace brick heal
    
    Problem: When features.cache-invalidation is ON, a lot of
    ec_notify function gets called which leads to launch of
    too many heals. This leads to no heal completion,
    which causes accumulation of heals.
    
    Solution: ec_launch_replace_heal should not be launch
    for every event. Replace brick will trigger a child up
    event and then only this heal function should be called.
    
    Change-Id: I57b44c6a279d57230daea1d93229be6069245b7d
    BUG: 1342796
    Signed-off-by: Ashish Pandey <aspandey>
    Reviewed-on: http://review.gluster.org/14649
    Reviewed-by: Xavier Hernandez <xhernandez>
    Smoke: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>