[
https://issues.apache.org/jira/browse/HDDS-11715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17899058#comment-17899058
]
Ashish Kumar commented on HDDS-11715:
-------------------------------------
[~erose] Yes from SCM point of view most of the time we always checks delete
processing count at once.
And with the recent metrics
[change|https://github.com/apache/ozone/pull/7249/files#:~:text=).isOpen())%20%7B-,metrics.incrSkippedTransaction()%3B,-%7D]
it helps even more whether there are too many transactions which are getting
skipped in each iteration.
>From recon point of view we don't want to show at individual block level but
>to show at different "container state" level for which delete transactions are
>present in SCM. This may not be useful in very large scale environment because
>it is expected that most of the containers will be in CLOSED state and scm
>will process delete to datanode.
> 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]
