Uploaded image for project: 'Apache Ozone'
  1. Apache Ozone
  2. HDDS-8387 Container and volume scanners phase II
  3. HDDS-7096

Clarify locations of on-demand scanning

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None
    • None

    Description

      Currently it is difficult to tell whether an IOException will cause a container to be marked unhealthy or not. The exception must be traced all the way up the stack checking each frame to see if the caller is moving the container to unhealthy. The goal of this jira is to clarify which operations cause a container to be marked unhealthy at the code level.

      In HDDS-7095 a general place was given for on-demand scanning. Clarify and move the places where on-demand scans are added if necessary.

      Attachments

        Issue Links

          is related to

          Sub-task - The sub-task of the issue HDDS-9736 Use scanner to mark containers unhealthy on the write path

          • Major - Major loss of function.
          • Open
          is required by

          Sub-task - The sub-task of the issue HDDS-7094 Enable Datanode side CRC checks by default

          • Major - Major loss of function.
          • Resolved
          relates to

          Sub-task - The sub-task of the issue HDDS-6549 Do not mark container replica as unhealthy on write failure

          • Major - Major loss of function.
          • Open

          Sub-task - The sub-task of the issue HDDS-7095 Allow containers to be prioritized for health scanning

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              erose Ethan Rose
              erose Ethan Rose
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: