[HDDS-3486] Recon cannot track missing containers that were created and went missing while it is down.

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.0.0
• Fix Version/s: 1.4.0
• Component/s: Ozone Recon
• Labels: pull-request-available
• Target Version/s: 1.4.0
• Assignee: Devesh Kumar Singh
• Reporter: Aravindan Vijayan
• Created: 24/Apr/20 23:14
• Updated: 22/Dec/22 08:42
• Resolved: 22/Dec/22 08:42

Description

Since Recon relies on Container reports from DNs to track replicas, if a new container was created and went missing when Recon was down, it will not be able to tag it as a missing container.

Issue Links

• Dependency: HDDS-7516 Implement SCM getDBUpdates endpoint
• links to: GitHub Pull Request #3947