mjhjmtu

Our snapshopt scheduler setup on our gluster nodes stopped working and upon investigation, I found that one of the bricks(test1.example.com:/data/brick) was down so I restarted the gluster service on that node to bring the brick backup online. I waited for the snapshot scheduler to kickoff again, but it failed. Upon using command gluster volume heal test_volume info I get the output below showing that there are two files on Brick test3.example.com:/data/brick needing heal. This has been like that for two days and no change. Is there a way for me to clear the backlog of files needing to be healed on brick test3.example.com:/data/brick. Would the backlog of files needing to be healed have caused the snapshot scheduler to not work?

Brick test1.example.com:/data/brick
Status: Connected
Number of entries: 0

Brick test2.example.com:/data/brick
Status: Connected
Number of entries: 0

Brick test3.example.com:/data/brick
<gfid:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx>
<gfid:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx>
Status: Connected
Number of entries: 2

I am at a loss as to what is preventing the snapshot scheduler from working again and why the backlog on brick test3 has been like that for days. Any assistance with this would be appreciated.