hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9976) Don't create duplicated TableName objects
Date Fri, 22 Nov 2013 16:26:37 GMT

    [ https://issues.apache.org/jira/browse/HBASE-9976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13830090#comment-13830090
] 

stack commented on HBASE-9976:
------------------------------

IIRC, there was an option in client to do full scan of meta table on startup.  Could do something
like that in background rather than fetch the next ten under a lock.

Patch lgtm.  It is an improvement.



> Don't create duplicated TableName objects
> -----------------------------------------
>
>                 Key: HBASE-9976
>                 URL: https://issues.apache.org/jira/browse/HBASE-9976
>             Project: HBase
>          Issue Type: Bug
>          Components: Client, regionserver
>    Affects Versions: 0.98.0, 0.96.0
>            Reporter: Nicolas Liochon
>            Assignee: Nicolas Liochon
>             Fix For: 0.98.0, 0.96.1
>
>         Attachments: 9976.v1.patch, 9976.v10.patch, 9976.v11.patch, 9976.v4.patch, 9976.v6.patch,
9976.v7.patch, 9976.v7.patch, 9976.v8.patch, 9976.v8.patch, 9976.v9.patch
>
>
> A profiling show that the table name is reponsible for 25% of the memory needed to keep
the region locations. As well, comparisons will be faster if two identical table names are
a single java object.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message