[
https://issues.apache.org/jira/browse/HBASE-13518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14515877#comment-14515877
]
Enis Soztutar commented on HBASE-13518:
---------------------------------------
+1.
> Typo in hbase.hconnection.meta.lookup.threads.core parameter
> ------------------------------------------------------------
>
> Key: HBASE-13518
> URL: https://issues.apache.org/jira/browse/HBASE-13518
> Project: HBase
> Issue Type: Improvement
> Reporter: Enis Soztutar
> Assignee: Devaraj Das
> Fix For: 2.0.0, 1.2.0
>
> Attachments: 13518-1.txt
>
>
> A possible typo coming from patch in HBASE-13036.
> I think we want {{hbase.hconnection.meta.lookup.threads.core}}, not
> {{hbase.hconnection.meta.lookup.threads.max.core}} to be in line with the
> regular thread pool configuration.
> {code}
> //To start with, threads.max.core threads can hit the meta
> (including replicas).
> //After that, requests will get queued up in the passed queue,
> and only after
> //the queue is full, a new thread will be started
> this.metaLookupPool = getThreadPool(
> conf.getInt("hbase.hconnection.meta.lookup.threads.max", 128),
> conf.getInt("hbase.hconnection.meta.lookup.threads.max.core",
> 10),
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
