[
https://issues.apache.org/jira/browse/HDDS-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated HDDS-6056:
------------------------------------
Description:
When the system goes through deletes, the containers tracked in OM metadata can
become a subset of the actual containers in the system. The SCM is a more up to
date supplier of container metadata. Hence, recon should use its SCM metadata
to give out the <containerId --> numKeys> API response.
For the numKeys, it can use the reverse mapping between container -> keys in
its rocksdb.
was:When the system goes through deletes, the containers tracked in OM
metadata can become a subset of the actual containers in the system. The SCM is
a more up to date supplier of container metadata. Hence, recon should use its
SCM metadata to give out the <containerId --> numKeys> API response.
> Recon /containers endpoint should return SCM container data instead of OM
> container data.
> -----------------------------------------------------------------------------------------
>
> Key: HDDS-6056
> URL: https://issues.apache.org/jira/browse/HDDS-6056
> Project: Apache Ozone
> Issue Type: Bug
> Components: Ozone Recon
> Affects Versions: 1.2.0
> Reporter: Aravindan Vijayan
> Priority: Major
>
> When the system goes through deletes, the containers tracked in OM metadata
> can become a subset of the actual containers in the system. The SCM is a more
> up to date supplier of container metadata. Hence, recon should use its SCM
> metadata to give out the <containerId --> numKeys> API response.
> For the numKeys, it can use the reverse mapping between container -> keys in
> its rocksdb.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
