[jira] [Comment Edited] (LENS-993) Estimate thread pool does not grow beyond minimum pool size.

["Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LENS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15209853#comment-15209853 ] 

Amareshwari Sriramadasu edited comment on LENS-993 at 3/24/16 6:34 AM:
-----------------------------------------------------------------------

As Executors.newCachedThreadPool could become problematic on a heavily loaded server, I'm planning to create ThreadPoolExecutor with SynchronousQueue as in newCachedThreadPool, but set max pool size to lower value than INT.MAX_VALUE.
The doc at http://dev.bizo.com/2014/06/cached-thread-pool-considered-harmlful.html was useful.


was (Author: amareshwari):
As Executors.newCachedThreadPool could become problematic on a heavily loaded server, I'm planning to create ThreadPoolExecutor with ArrayBlockingQueue instead of LinkedBlockingQueue.
The doc at http://dev.bizo.com/2014/06/cached-thread-pool-considered-harmlful.html was useful.

> Estimate thread pool does not grow beyond minimum pool size.
> ------------------------------------------------------------
>
>                 Key: LENS-993
>                 URL: https://issues.apache.org/jira/browse/LENS-993
>             Project: Apache Lens
>          Issue Type: Bug
>          Components: server
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Amareshwari Sriramadasu
>             Fix For: 2.6
>
>
> We noticed that there are only 3 threads (the min pool size) on the server and not growing. And 3 threads are blocked on JDBC connection and all subsequent estimate calls timeout as there are no threads.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)