hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Heng Chen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16025) Cache table state to reduce load on META
Date Wed, 03 Aug 2016 07:56:20 GMT

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

Heng Chen commented on HBASE-16025:
-----------------------------------

Yeah, it is a problem.  For one request, i think we could cache the state after get the state
firstly from meta during retry.  wdyt?

> Cache table state to reduce load on META
> ----------------------------------------
>
>                 Key: HBASE-16025
>                 URL: https://issues.apache.org/jira/browse/HBASE-16025
>             Project: HBase
>          Issue Type: Improvement
>          Components: Client
>            Reporter: Gary Helmling
>            Assignee: Gary Helmling
>            Priority: Critical
>             Fix For: 2.0.0
>
>
> HBASE-12035 moved keeping table enabled/disabled state from ZooKeeper into hbase:meta.
 When we retry operations on the client, we check table state in order to return a specific
message if the table is disabled.  This means that in master we will be going back to meta
for every retry, even if a region's location has not changed.  This is going to cause performance
issues when a cluster is already loaded, ie. in cases where regionservers may be returning
CallQueueTooBigException.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message