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

Use scanner to mark containers unhealthy on the write path

    XMLWordPrintableJSON

Details

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

    Description

      Currently if there is any exception on the write path, containers will be marked unhealthy, which is a terminal state. Some of these errors do not affect the contents of these containers so they should not actually be marked unhealthy. This jira proposes closing a container normally if an error is encountered, and queueing it for on demand scanning once the close finishes. After this change, the scanner would be the only thing that can mark a container unhealthy.

      Attachments

        Issue Links

          relates to

          Sub-task - The sub-task of the issue HDDS-7096 Clarify locations of on-demand scanning

          • Major - Major loss of function.
          • Open

          Activity

            People

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

              Dates

                Created:
                Updated: