Description of problem:
====================
When a brick is down and heals are pending, there is no point scanning all the entries of indices xattrops and then figuring out the sink brick is still down, as this means wasted cpu cycles.
Suppose in  a 1x(4+2) volume , one brick is down, and a user created or modified say 1million files, the self healdeamon must not scroll/scan through all the pending heal entries in indices/xattrops and then decide not to heal as sink is still down.
Instead it can check if sink is still down and then only scan indices/xattrops

yes there can be cases where the down brick is up and another brick went down, so we should consider all these cases
Hence proposing as an RFE



Version-Release number of selected component (if applicable):
======
3.8.4-28

Steps to Reproduce:
1.create a 1x(4+2) volume
2.bring down b1
3.create 1million or say even 1lakh files

heal deamon now scans periodically all the entries in xattrops even when brick is down, which is of no use


Actual results:


Expected results:


Additional info: