[
https://issues.apache.org/jira/browse/HDDS-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16645506#comment-16645506
]
Shashikant Banerjee commented on HDDS-550:
------------------------------------------
Thanks [~elek] for the confirmation.
As per offline discussion with [~jnp], removed the ExecutorMap in
XceiverServerRatis with a list. Fixed the CloseContainerHandlingByClient tests
and removed the TestContainerStateMachine tests which were basically verifying
the synchronization between write chunks, putBlock and CloseContainer as with
this Jira, there won' be any such synchronization required.
Other test failures are not related.
> 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
> Attachments: HDDS-550.001.patch, HDDS-550.002.patch,
> HDDS-550.003.patch, HDDS-550.004.patch, HDDS-550.005.patch, HDDS-550.006.patch
>
>
> 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]
