devmadhuu opened a new pull request, #4509:
URL: https://github.com/apache/ozone/pull/4509
Container Level Info (Tab1): A new API
"api/v1/containers/insights/nonscmcontainers" will present the container level
info showing mismatch between SCM and OM. Some containers are deleted in SCM
but seem to be referred to by files/keys in OM, So recon needs to detect if any
container is missing or not from OM perspective. This is a data loss situation.
This API will be consumed by Recon new tab/page. This API will only identify
and list such containers along with number of keys. Recon UI can later query
"api/v1/containers/<containerId>/keys" to get details of keys mapped to such
containers.
Rest API Response for "api/v1/containers/insights/nonscmcontainers"
[
{
"containerId" : 1,
"numberOfKeys" : 3,
"pipelines" : [
pipelineId: 1423ghjds832403232,
pipelineId: 32vds94943fsdh4443,
pipelineId: 32vds94943fsdhs443
],
"existsAt" : "OM"
}
]
Here in this tab, below list of containers will be shown along with their
key mappings.
<img width="976" alt="image"
src="https://user-images.githubusercontent.com/20607992/229130680-28104ea6-77de-40b0-8587-d506bcb36df0.png";>
So this PR covers the situation of "Container is present in OM, but not in
SCM."
https://issues.apache.org/jira/browse/HDDS-8326
## How was this patch tested?
This patch was tested using Junit test cases.
--
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]
![https://user-images.githubusercontent.com/20607992/229130680-28104ea6-77de-40b0-8587-d506bcb36df0.png"](https://user-images.githubusercontent.com/20607992/229130680-28104ea6-77de-40b0-8587-d506bcb36df0.png"){kind=link}