You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Liu Shaohui (JIRA)" <ji...@apache.org> on 2015/03/27 13:53:52 UTC
[jira] [Created] (HBASE-13348) Separate the thread number configs
for meta server and server operations
Liu Shaohui created HBASE-13348:
-----------------------------------
Summary: Separate the thread number configs for meta server and server operations
Key: HBASE-13348
URL: https://issues.apache.org/jira/browse/HBASE-13348
Project: HBase
Issue Type: Bug
Reporter: Liu Shaohui
Assignee: Liu Shaohui
Currently, the config keys for thread number of meta server and server operations in HMaster are same:
See: HMaster.java #993
{code}
this.service.startExecutorService(ExecutorType.MASTER_SERVER_OPERATIONS,
conf.getInt("hbase.master.executor.serverops.threads", 5));
this.service.startExecutorService(ExecutorType.MASTER_META_SERVER_OPERATIONS,
conf.getInt("hbase.master.executor.serverops.threads", 5));
{code}
In large cluster, we usually enlarge the thread number for server operation separately to make the master handle regionserver shutdown events quickly in some extremely cases.
So I think we need separate the thread number config for the two operations.
Suggestions are welcomed. Thanks~
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)