[
https://issues.apache.org/jira/browse/RATIS-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Doroszlai updated RATIS-1419:
------------------------------------
Fix Version/s: 2.3.0
(was: 1.1.0)
> Use cached thread pools in DataStreamManagement
> -----------------------------------------------
>
> Key: RATIS-1419
> URL: https://issues.apache.org/jira/browse/RATIS-1419
> Project: Ratis
> Issue Type: Improvement
> Components: Streaming
> Reporter: Tsz-wo Sze
> Assignee: Tsz-wo Sze
> Priority: Minor
> Fix For: 2.3.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In DataStreamManagement, the requestExecutor and writeExecutor are created by
> Executors.newFixedThreadPool(..). A drawback is that the threads in the
> fixed thread pool are using resource even if the executors are idle.
> One way to improve it is to use Executors.newCachedThreadPool(..). However,
> all the newCachedThreadPool(..) methods provided by Executors do not take a
> maximumPoolSize parameter. We will define a newCachedThreadPool(..) method
> which takes a maximumPoolSize parameter.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
