[HDDS-7364] Improved container scanning

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.5.0
• Target Version/s: 1.5.0
• Assignee: Ethan Rose
• Reporter: Ethan Rose
• Created: 19/Oct/22 22:23
• Updated: 14/Mar/24 21:02
• Resolved: 14/Mar/24 21:02

Description

Ozone's container scanners are currently off by default. This jira is improve and test container scanning to better detect corrupted replicas so we can turn the feature on by default.

Issue Links

• is a parent of: HDDS-7300 Race condition between full data scan and block deletion
• split from: HDDS-6548 HDDS Stability Fixes and Improvements
• split to: HDDS-8387 Container and volume scanners phase II

Sub-Tasks

• Allow containers to be prioritized for health scanning: Resolved
• Container Scanner should be enabled by default: Resolved
• Container scanner log output lacks useful information: Resolved
• Coordinate on demand and background container scanners: Resolved
• Integrate container and volume scanners: Resolved
• Avoid false positive failures in scanners: Resolved
• Improve scanner integration tests: Resolved
• Metadata scanner should not scan unhealthy containers: Resolved
• Container scanner incorrectly marks containers unhealthy when DN is shutdown: Resolved
• Improve Volume Scanner Health checks: Resolved
• Persist reason for container replica being marked unhealthy: Resolved
• Container log should write to separate file: Resolved
• Update default config values for container scanners: Resolved
• Intermittent timeout in TestBackgroundContainerDataScannerIntegration: Resolved