[
https://issues.apache.org/jira/browse/HDDS-15456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sreeja updated HDDS-15456:
--------------------------
Description:
Implement a read-only SCM metadata scanner that opens the provided {{scm.db}}
and performs container lookups in the {{containers}} column family. For each
unique container ID discovered during the DataNode container scan HDDS-15455,
determine whether the container exists in SCM metadata and retrieve its
lifecycle state.
Build a lookup result containing:
* *{{NOT_IN_SCM}}* for container IDs that do not exist in SCM metadata.
* *{{DELETED}}* for container IDs whose SCM lifecycle state is {{{}DELETED{}}}.
Containers present in SCM with any other lifecycle state do not need to be
included in the result.
The resulting lookup information should be used by subsequent analysis steps to
identify orphan containers (wrt SCM) and deleted-but-present containers i.e
containers whose state is "DELETED" in scm metadata but is still present in the
datanode /current directory
was:
Implement a read-only SCM metadata scanner that opens the provided {{scm.db}}
and performs container lookups in the {{containers}} column family. For each
unique container ID discovered during the DataNode container scan HDDS-15455,
determine whether the container exists in SCM metadata and retrieve its
lifecycle state.
Build a lookup result containing:
* *{{NOT_IN_SCM}}* for container IDs that do not exist in SCM metadata.
* *{{DELETED}}* for container IDs whose SCM lifecycle state is {{{}DELETED{}}}.
Containers present in SCM with any other lifecycle state do not need to be
included in the result.
The resulting lookup information should be used by subsequent analysis steps to
identify orphan containers (wrt SCM) and deleted-but-present containers.
> Add SCM DB lookup and identify orphan(wrt SCM) and deleted-but-present
> containers
> ---------------------------------------------------------------------------------
>
> Key: HDDS-15456
> URL: https://issues.apache.org/jira/browse/HDDS-15456
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Sreeja
> Assignee: Sreeja
> Priority: Major
>
> Implement a read-only SCM metadata scanner that opens the provided {{scm.db}}
> and performs container lookups in the {{containers}} column family. For each
> unique container ID discovered during the DataNode container scan HDDS-15455,
> determine whether the container exists in SCM metadata and retrieve its
> lifecycle state.
> Build a lookup result containing:
> * *{{NOT_IN_SCM}}* for container IDs that do not exist in SCM metadata.
> * *{{DELETED}}* for container IDs whose SCM lifecycle state is
> {{{}DELETED{}}}.
> Containers present in SCM with any other lifecycle state do not need to be
> included in the result.
> The resulting lookup information should be used by subsequent analysis steps
> to identify orphan containers (wrt SCM) and deleted-but-present containers
> i.e containers whose state is "DELETED" in scm metadata but is still present
> in the datanode /current directory
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
