[
https://issues.apache.org/jira/browse/HDDS-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shashikant Banerjee updated HDDS-348:
-------------------------------------
Description: Currently all the ops in
ContainerStateMachine#applyTransaction are processed sequentially by the
ContainerStateMachine. However these ops can be parallelized by having a
configurable no of executors where a certain executor for a container can be
chosen from the pool of executors by hashing the containerID. (was: Currently
all the ops in ContainerStateMachine#applyTransaction are processed
sequentially by the ContainerStateMachine. However these ops can be
parallelized by having a per container executor. )
> Parallalize container ops in ContainerStateMachine
> --------------------------------------------------
>
> Key: HDDS-348
> URL: https://issues.apache.org/jira/browse/HDDS-348
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Datanode
> Affects Versions: 0.2.1
> Reporter: Mukul Kumar Singh
> Assignee: Mukul Kumar Singh
> Priority: Major
> Fix For: 0.2.1
>
> Attachments: HDDS-348.001.patch, HDDS-348.002.patch
>
>
> Currently all the ops in ContainerStateMachine#applyTransaction are processed
> sequentially by the ContainerStateMachine. However these ops can be
> parallelized by having a configurable no of executors where a certain
> executor for a container can be chosen from the pool of executors by hashing
> the containerID.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
