accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1224) Custom Thread Pool in BatchScanner
Date Thu, 28 Mar 2013 20:55:17 GMT

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

Keith Turner commented on ACCUMULO-1224:
----------------------------------------

If an external thread pool can be passed in, then the close() method would need to change.
 close() currently shuts down the thread pool.  Also other parts of the code check if the
threadPool was shutdown.   Instead of shutting the thread pool down if its external, I suppose
it would need to make any work queued on the thread pool be a noop when it finally runs. 


For the API, maybe create something like BatchWriterConfig to avoid muddying the API.



                
> Custom Thread Pool in BatchScanner
> ----------------------------------
>
>                 Key: ACCUMULO-1224
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1224
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: client
>            Reporter: Roshan Punnoose
>            Assignee: Billie Rinaldi
>            Priority: Minor
>         Attachments: threadPool.patch
>
>
> I would like the ability to supply my own ThreadPool(ExecutorService) when the BatchScanner
is created. This would give me the ability to throttle how many threads are created in an
application.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message