[
https://issues.apache.org/jira/browse/HDDS-1757?focusedWorklogId=271232&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-271232
]
ASF GitHub Bot logged work on HDDS-1757:
----------------------------------------
Author: ASF GitHub Bot
Created on: 02/Jul/19 21:17
Start Date: 02/Jul/19 21:17
Worklog Time Spent: 10m
Work Description: bharatviswa504 commented on issue #1048: HDDS-1757. Use
ExecutorService in OzoneManagerStateMachine.
URL: https://github.com/apache/hadoop/pull/1048#issuecomment-507848143
Thank You @anuengineer for the review.
As suggested, used HadoopExecutor API, and also invoked shutdown during the
stop.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 271232)
Time Spent: 40m (was: 0.5h)
> 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: 40m
> 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]
