[
https://issues.apache.org/jira/browse/HDDS-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16877351#comment-16877351
]
Hudson commented on HDDS-1757:
------------------------------
FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #16855 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/16855/])
HDDS-1757. Use ExecutorService in OzoneManagerStateMachine. (#1048) (aengineer:
rev 91cc19722796877f134fd04f60229ac47a1bd6e0)
* (edit)
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/ratis/OzoneManagerStateMachine.java
> Use ExecutorService in OzoneManagerStateMachine
> -----------------------------------------------
>
> Key: HDDS-1757
> URL: https://issues.apache.org/jira/browse/HDDS-1757
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Bharat Viswanadham
> Assignee: Bharat Viswanadham
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> In the current code in applyTransaction we have
> CompletableFuture<Message> future = CompletableFuture
> .supplyAsync(() -> runCommand(request, trxLogIndex)); We are using
> ForkJoin#commonPool.
> With the current approach we have 2 issues:
> # Thread exhausts when using this common pool.
> # Not a good practice of using common pool. Found some issues in our testing
> by using similarly in RatisPipelineUtils.
> # OM DB's across replica can be out of sync when the apply transactions are
> applied in out of order.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
