[
https://issues.apache.org/jira/browse/HDDS-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887783#comment-16887783
]
Hudson commented on HDDS-1767:
------------------------------
FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #16946 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/16946/])
HDDS-1767: ContainerStateMachine should have its own executors for (github: rev
23e9bebe13bd2c79494b1caaa22763914b38b74f)
* (edit)
hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/common/transport/server/ratis/ContainerStateMachine.java
* (edit)
hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/common/transport/server/ratis/XceiverServerRatis.java
> ContainerStateMachine should have its own executors for executing
> applyTransaction calls
> ----------------------------------------------------------------------------------------
>
> Key: HDDS-1767
> URL: https://issues.apache.org/jira/browse/HDDS-1767
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Lokesh Jain
> Assignee: Lokesh Jain
> Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Currently ContainerStateMachine uses the executors provided by
> XceiverServerRatis for executing applyTransaction calls. This would result in
> two or more ContainerStateMachine to share the same set of executors. Delay
> or load in one ContainerStateMachine would adversely affect the performance
> of other state machines in such a case. It is better to have separate set of
> executors for each ContainerStateMachine.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
