[
https://issues.apache.org/jira/browse/HDDS-12619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Doroszlai resolved HDDS-12619.
-------------------------------------
Fix Version/s: 2.1.0
Resolution: Implemented
> Optimize Recon Om Container Mismatch API
> -----------------------------------------
>
> Key: HDDS-12619
> URL: https://issues.apache.org/jira/browse/HDDS-12619
> Project: Apache Ozone
> Issue Type: Improvement
> Components: Ozone Recon
> Reporter: Swaminathan Balachandran
> Assignee: Swaminathan Balachandran
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.1.0
>
>
> Currently the Container mismatch API in recon loads up the entire
> ContainerMetaData from ContainerKeyPrefix table and figures out the container
> mismatches between OM & SCM. The implication is that the ContainerKeyPrefix
> table will have as many keys as there there in OM. In case there are too many
> keys even for loading a small page too many containers would be brought into
> memory and the result would be eventually discarded because of the page size
> limit. Instead of this we should implement an container iterator for the
> containerKeyPrefix table which would iterate on containers sequentially in a
> sorted fashion along with the scm containerManager iterator and diff would be
> figured out based on the merging these 2 container list. We can save on a lot
> of iops & improve the latency of this api by a lot.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
