[
https://issues.apache.org/jira/browse/HDDS-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham updated HDDS-1757:
-------------------------------------
Description:
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.
was:
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.
# OM DB's across replica can be out of sync when the apply transactions are
applied in out of order.
> 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
>
> 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]
