You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Umesh Chaudhary (JIRA)" <ji...@apache.org> on 2016/09/12 06:13:20 UTC

[jira] [Commented] (FLUME-2692) Make the number of threads in AsyncHbaseSink configurable

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

Umesh Chaudhary commented on FLUME-2692:
----------------------------------------

Hello [~jrufus], Are you still working on this? If not, I can work on this. 
In my opinion,  there should be some formula to decide Hbase client connection threads and that should be well documented. Just like 2 * num_processors, which is the simplest way here to decide parallelism. Want to know you thoughts though.

I see that we could utilize following constructor:
 public NioClientSocketChannelFactory(Executor bossExecutor, Executor workerExecutor, int bossCount, int workerCount) 


> Make the number of threads in AsyncHbaseSink configurable
> ---------------------------------------------------------
>
>                 Key: FLUME-2692
>                 URL: https://issues.apache.org/jira/browse/FLUME-2692
>             Project: Flume
>          Issue Type: Improvement
>            Reporter: Johny Rufus
>            Assignee: Johny Rufus
>
> When creating the HbaseClient, NioClientSocketChannelFactory passed in, can take a configurable number of threads as parameter. The default number of worker threads created is 2 * num_processors (similar on both client and server side)



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