Gluster snapshot scheduler stopped working and pending backlog entries not healing

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












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.







share|improve this question























    up vote
    0
    down vote

    favorite












    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.







    share|improve this question





















      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      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.







      share|improve this question











      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.









      share|improve this question










      share|improve this question




      share|improve this question









      asked May 18 at 13:26









      TeNaJ Systems

      394




      394

























          active

          oldest

          votes











          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "106"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );








           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f444606%2fgluster-snapshot-scheduler-stopped-working-and-pending-backlog-entries-not-heali%23new-answer', 'question_page');

          );

          Post as a guest



































          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes










           

          draft saved


          draft discarded


























           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f444606%2fgluster-snapshot-scheduler-stopped-working-and-pending-backlog-entries-not-heali%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

          How to check contact read email or not when send email to Individual?

          Bahrain

          Postfix configuration issue with fips on centos 7; mailgun relay