[jira] [Updated] (HBASE-3508) LruBlockCache statistics thread should have a name

["Phabricator (Updated) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-3508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Phabricator updated HBASE-3508:
-------------------------------

    Attachment: D2853.1.patch

mbautin requested code review of "[jira] [HBASE-3508] [89-fb] LruBlockCache statistics thread should have a name".
Reviewers: Liyin, Kannan, aaiyer, todd, JIRA

  Pulling in the small patch from trunk: HBASE-3508.
  Original description below.

  Currently it's just an unnamed threadpool. It's annoying.


TEST PLAN
  Run a minicluster unit test in a debugger. Ensure that the cache stats thread has a name.

REVISION DETAIL
  https://reviews.facebook.net/D2853

AFFECTED FILES
  src/main/java/org/apache/hadoop/hbase/io/hfile/LruBlockCache.java

MANAGE HERALD DIFFERENTIAL RULES
  https://reviews.facebook.net/herald/view/differential/

WHY DID I GET THIS EMAIL?
  https://reviews.facebook.net/herald/transcript/6477/

Tip: use the X-Herald-Rules header to filter Herald messages in your client.

                
> LruBlockCache statistics thread should have a name
> --------------------------------------------------
>
>                 Key: HBASE-3508
>                 URL: https://issues.apache.org/jira/browse/HBASE-3508
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Trivial
>             Fix For: 0.90.1
>
>         Attachments: D2853.1.patch, hbase-3508.txt
>
>
> Currently it's just an unnamed threadpool. It's annoying.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira