[HDDS-8214] Recon - OM DB Insights

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Ozone Recon
• Labels: pull-request-available
• Epic Link: Recon - OM DB Insights, SCM DB Insights, Container Level Keys Info
• Assignee: Devesh Kumar Singh
• Reporter: Devesh Kumar Singh
• Created: 20/Mar/23 05:13
• Updated: 11/May/23 11:45

Description

Container Level Info (Tab1): A new tab as shown below will present the container level info showing mismatch between SCM and OM. Some containers are deleted in SCM but seem to be referred to by files/keys in OM, So recon needs to detect if any container is missing or not from OM perspective. This requirement came up due to missing containers in one of our test cluster where OM still maintains those deleted containers along with key mapping and those keys cannot be reached as containers doesn’t exists at SCM, which is a data loss situation.Issue details are at https://issues.apache.org/jira/browse/HDDS-7701.

Key Level Info (Tab 2): A new tab as shown above will be used to represent below information.

• List of open keys based on limit.
• List of pending delete keys based on limit.
• Amount of data mapped to pending delete keys
• Keys that are mapped to containers in DELETED state in SCM
• Should never happen, but we want to show this in case if any.

Issue Links

• is duplicated by: HDDS-8301 Recon should report when blocks in OM DB reference missing containers on SCM
• links to: GitHub Pull Request #4516

Sub-Tasks

• Container Level Info - OM DB Insights: Resolved
• Recon - Orphan Key Level Info - OM DB Insights: Patch Available
• Container Level Info - OM DB Insights - Container is present in SCM, but not in OM: Resolved
• Recon UI:OM DB Insights Changes: Resolved
• API Documentation for OM Key Level Info and Container Mismatch and SCM DB Insights Info: Resolved