hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Bieniosek (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HBASE-4) hbase client makes too many requests against .META.,,1 table: caching of .META.,,1 lookups is broken?
Date Tue, 05 Feb 2008 19:55:15 GMT

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

Michael Bieniosek resolved HBASE-4.
-----------------------------------

    Resolution: Invalid

I tried again with an hbase closer to trunk, and the problem went away.

> hbase client makes too many requests against .META.,,1 table: caching of .META.,,1 lookups
is broken?
> -----------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-4
>                 URL: https://issues.apache.org/jira/browse/HBASE-4
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: client
>            Reporter: Michael Bieniosek
>
> We're running a high load of random reads through a single hbase rest server.  When I
look at the 60010 master servlet, there are a very high number of hits to the server hosting
.META.,,1.  That server has 4000 requests in the last "3 seconds", the server hosting ROOT
(and two other regions which shouldn't be getting reads) has 80 requests, and all the other
regionservers have less.  
> This doesn't seem right: shouldn't the single hbase client be caching table lookups?
> This appears to be a hurdle for scaling our random read rate.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message