[
https://issues.apache.org/jira/browse/HDDS-11715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17898576#comment-17898576
]
Ashish Kumar commented on HDDS-11715:
-------------------------------------
In recent
[change|https://github.com/apache/ozone/pull/7249/files#:~:text=).isOpen())%20%7B-,metrics.incrSkippedTransaction()%3B,-%7D]
one metric is added to show how many transactions we are skipping in the
delete iteration inside scm. Those skipped transactions belongs to open
containers or max retry transactions or any inadequate replica case. This can
help in whether skip transactions are too many in the iteration or it is just
minimal.
This metrics already gives some level of idea about how SCM delete is
progressing. To get complete view of scm deleted blocks data we thought if
recon can show in some way.
For tool already rocksdb can be quried using ldb and it can show.
> Display scm block delete information for faster debugging
> ---------------------------------------------------------
>
> Key: HDDS-11715
> URL: https://issues.apache.org/jira/browse/HDDS-11715
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Ashish Kumar
> Assignee: Tejaskriya Madhan
> Priority: Major
>
> How many transactions are present in open/closed/deleted/other state
> container in scm deleted table. This can be looked from recon side if DB can
> sync and display these information.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
