Uploaded image for project: 'Apache Ozone'
  1. Apache Ozone
  2. HDDS-7364 Improved container scanning
  3. HDDS-8191

Avoid false positive failures in scanners

Attach filesAttach ScreenshotVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

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

    Description

      Sometimes volume or container scan may fail due to external issues in the file system or operation system that do not affect the content of the containers or volumes and are caused by simple admin mistakes. This jira proposes having the following failures be logged by the scanners but not cause their contents to be marked unhealthy:

      • Too many open files
        • Can be fixed by the admin adjusting the file descriptor limit for the node.
      • Permission denied for reading or writing.
        • Can be fixed by the admin fixing filesystem permissions.
      • No space left on device
        • Should be prevented by configuring hdds.datanode.dir.du.reserved.percent to leave some free space on the volume.
        • Failing full volumes could put an already full cluster in a worse state by triggering replication.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

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

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment