[
https://issues.apache.org/jira/browse/KUDU-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16436717#comment-16436717
]
HeLifu commented on KUDU-2211:
------------------------------
here are another two solutions:
1.move consensus-metadata to 'WAL'(which is SSD maybe) and make a link to the
new dir;
2.Spread metadata across multiple data directories: KUDU-2117
So, this issue could be closed. :)
> improve the thread pool for rpc service
> ---------------------------------------
>
> Key: KUDU-2211
> URL: https://issues.apache.org/jira/browse/KUDU-2211
> Project: Kudu
> Issue Type: Improvement
> Components: rpc
> Affects Versions: 1.5.0
> Reporter: HeLifu
> Priority: Minor
>
> in user mail list, Lee King modified his config of 'rpc_num_threads' to 128
> for consensus stability, but it will waste too much resource. maybe we could
> do some improvement:
> 1) different rpc service use different config of 'rpc_num_thread';
> 2) use 'threadpool' instead of 'std::vector<scoped_refptr<kudu::Thread> >
> threads_', just like negotiation pool does;
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
