Uploaded image for project: 'Apache Ozone'
  1. Apache Ozone
  2. HDDS-6548 HDDS Stability Fixes and Improvements
  3. HDDS-8115

Do not use block count to determine if containers are empty

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.4.0
    • None

    Description

      Ozone currently uses a block count metadata field for each container replica to determine whether it is empty. This counter can be incorrect in some cases and is difficult to maintain. It is only used to determine whether the container is empty. In this case, it would be simpler to have a an isEmpty boolean for each container that starts as false and is set to true when a delete block is processed and the block table is empty.

      Attachments

        Issue Links

          is related to

          Sub-task - The sub-task of the issue HDDS-8141 Exception "Non-force deletion of non-empty container is not allowed" in datanode logs

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. HDDS-9550 Container report shows missing containers when they actually appear empty

          • Blocker - Blocks development and/or testing work, production could not run
          • Resolved
          relates to

          Sub-task - The sub-task of the issue HDDS-8908 Intermittent failure in TestBlockDeletion#testBlockDeletion

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

          Web Link GitHub Pull Request #4655

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: