[
https://issues.apache.org/jira/browse/HDDS-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shashikant Banerjee updated HDDS-550:
-------------------------------------
Description:
As part of handling Node failures in Ozone, the block commit need to happen in
order inside ContainerStateMachine per container. With RATIS-341, it is
guaranteed that the applyTransaction calls for committing the write chunks
will be initiated only when the WriteStateMachine data for write Chunk
operations finish.
This Jira is aimed at making all the applyTransaction operations inside
ContainerStateMachine serial per container with a single thread Executor per
container handling all applyTransactions calls.
was:As part of handling Node failures in Ozone, the block commit need to
happen in order inside ContainerStateMachine per container.
> Serialize ApplyTransaction calls per Container in ContainerStateMachine
> -----------------------------------------------------------------------
>
> Key: HDDS-550
> URL: https://issues.apache.org/jira/browse/HDDS-550
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Shashikant Banerjee
> Assignee: Shashikant Banerjee
> Priority: Major
>
> As part of handling Node failures in Ozone, the block commit need to happen
> in order inside ContainerStateMachine per container. With RATIS-341, it is
> guaranteed that the applyTransaction calls for committing the write chunks
> will be initiated only when the WriteStateMachine data for write Chunk
> operations finish.
> This Jira is aimed at making all the applyTransaction operations inside
> ContainerStateMachine serial per container with a single thread Executor per
> container handling all applyTransactions calls.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
