[HBASE-13518] Typo in hbase.hconnection.meta.lookup.threads.core parameter

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.1.0, 2.0.0
• Assignee: Devaraj Das
• Reporter: Enis Soztutar
• Created: 21/Apr/15 00:43
• Updated: 03/Jul/15 23:38
• Resolved: 28/Apr/15 06:12

Description

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.

            //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),