[
https://issues.apache.org/jira/browse/HDDS-12620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Andika updated HDDS-12620:
-------------------------------
Target Version/s: (was: 2.0.1)
> Fix OM Mismatch Deleted Container API
> -------------------------------------
>
> Key: HDDS-12620
> URL: https://issues.apache.org/jira/browse/HDDS-12620
> Project: Apache Ozone
> Issue Type: Bug
> 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 first few
> ContainerMetaData records from ContainerKeyPrefix table. Then from the scm
> containerManager all deleted containers are iterated and checked against the
> records loaded from containerPrefixTable. If a deletedContainer is not
> present in the loaded list the results turn out to be empty even though there
> could be some records present in the containerPrefixTable in the next few
> pages. This could lead to a wrong result by setting the lastKey to null in
> case it couldn't find any records corresponding to a deletedContainer.
> Consider this example:
> ContainerPrefixTable has containerIds
> 1..100 1000-1100
> SCM has deletedContainerId
> 1000-1050
> Now if an api call is made with lastKey as 50 and limit as 50
> Now from the ContainerPrefix Table we would load only records 50-100
> From SCM ContainerManager we would load deleted Containers 1000-1050
> Since there is no intersection b/w these 2 containers then deletedContainers
> would never get loaded and would always be empty.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
