You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2018/06/19 15:15:00 UTC

[jira] [Commented] (HBASE-15654) Optimize client's MetaCache handling

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

stack commented on HBASE-15654:
-------------------------------

Meta perf is coming up more and more. In hbase2 we go to meta more for stuff like table state. Master does not currently cache the last thing read from meta though it is the only writer so meta is hit harder in hbase2. need to start working through these issues.

> Optimize client's MetaCache handling
> ------------------------------------
>
>                 Key: HBASE-15654
>                 URL: https://issues.apache.org/jira/browse/HBASE-15654
>             Project: HBase
>          Issue Type: Umbrella
>          Components: Client
>    Affects Versions: 1.3.0
>            Reporter: Mikhail Antonov
>            Assignee: Mikhail Antonov
>            Priority: Critical
>             Fix For: 3.0.0, 1.5.0, 2.2.0
>
>
> This is an umbrella jira to track all individual issues, bugfixes and small optimizations around MetaCache (region locations cache) in the client. Motivation is that under the load one could see a spikes in the number of requests going to meta - reaching tens of thousands requests per second.
> That covers issues when we clear entries from location cache unnecessary, as well as when we do more lookups than necessary when entries are legitimately evicted.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)