[
https://issues.apache.org/jira/browse/HDDS-15634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-15634:
----------------------------------
Labels: pull-request-available (was: )
> Avoid updating container delete transaction ID on SCM delete log append
> -----------------------------------------------------------------------
>
> Key: HDDS-15634
> URL: https://issues.apache.org/jira/browse/HDDS-15634
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: ChenXi
> Assignee: ChenXi
> Priority: Major
> Labels: pull-request-available
>
> When SCM handles DeleteScmKeyBlocks requests, AllocateScmBlock can see high
> tail latency because `SequenceIdGenerator#getNextId` waits for
> SCMStateMachine to finish applying
> DeletedBlockLogStateManagerImpl#addTransactionsToDB.
> Profiling shows a large part of addTransactionsToDB time is spent updating
> SCM-side ContainerInfo#deleteTransactionId.
> This field is not used by current SCM business logic, while DN-side delete
> transaction tracking is maintained independently.
> This ticket removes the SCM-side ContainerInfo#deleteTransactionId update
> from addTransactionsToDB to reduce unnecessary StateMachine apply work and
> improve write tail latency.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
