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

Provide CLI to do read-only scan of containers for debug purposes

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsAdd voteVotersWatch issueWatchersConvert to IssueLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

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

    Description

      Currently, when a container is marked unhealthy by the scanner, there isn't any information persisted as to why this this happened once the datanode logs roll off. In the future we may persist the reason to the container file (if it is still readable), but another option is to have an ozone debug command that can be run on the datanode that will do an on-demand, read-only check of the container and report what it finds.

      Attachments

        Issue Links

        Activity

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

          People

            Unassigned Unassigned Assign to me
            erose Ethan Rose

            Dates

              Created:
              Updated:

              Slack

                Issue deployment