Ashish Kumar created HDDS-13103:
-----------------------------------
Summary: Correct transaction metrics in SCMBlockDeletingService
Key: HDDS-13103
URL: https://issues.apache.org/jira/browse/HDDS-13103
Project: Apache Ozone
Issue Type: Improvement
Reporter: Ashish Kumar
NumBlockDeletionTransactionCreated and NumBlockDeletionTransactionCompleted
metrics are updated at each transaction level.
Whereas NumBlockDeletionTransactionSent, NumBlockDeletionTransactionSuccess and
NumBlockDeletionTransactionFailure are updated depending on the transactions
sent to DN. If the same transaction is sent to 3 DN(as blocks will reside in 3
DNs for Ratis-3), these metrics are updated 3 times.
By looking into below metrics it looks, 1731 transactions are sent and only 577
are completed. But actually 1731 = 577 * 3.
{code:java}
"name" :
"Hadoop:service=StorageContainerManager,name=SCMBlockDeletingService",
"modelerType" : "SCMBlockDeletingService",
"tag.Hostname" : "ccycloud-3.obsdeletion-719.root.comops.site",
"NumBlockDeletionCommandSent" : 3,
"NumBlockDeletionCommandSuccess" : 3,
"NumBlockDeletionCommandFailure" : 0,
"NumBlockDeletionTransactionSent" : 1731,
"NumBlockDeletionTransactionSuccess" : 1731,
"NumBlockDeletionTransactionFailure" : 0,
"NumBlockDeletionTransactionCompleted" : 577,
"NumBlockDeletionTransactionCreated" : 5672,
"NumSkippedTransactions" : 23909618,
"NumProcessedTransactions" : 1731, {code}
We should have proper naming or have consistent metrics for user to understand.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
