ArafatKhan2198 commented on PR #4266: URL: https://github.com/apache/ozone/pull/4266#issuecomment-1435993745
> I am not familiar with recon implementation. If the recon does respond correctly when key is removed from namespace, then I agree the best course of action for this issue is to ignore. When a key is deleted in an Ozone cluster, the Ozone Manager updates its OM-DB to reflect the deletion. This change is then detected by Recon during its next **incremental update** or **full snapshot scan**, depending on the mode in which Recon is operating. Once Recon detects the deletion, it updates its metadata store to reflect the change. Specifically, Recon updates the index associated with the deleted key to remove it from the index. This ensures that the deleted key is not included in any future searches or queries against the metadata store. Recon also retains a record of the deleted key in its metadata store inside the `DeletedTable`. This allows administrators to query the metadata store for deleted keys and to see when they were deleted. This information can be useful for auditing, compliance, and troubleshooting purposes. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
