[
https://issues.apache.org/jira/browse/HBASE-16025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16382613#comment-16382613
]
stack commented on HBASE-16025:
-------------------------------
hbase:meta is too loaded as it is. We see this in quite a few deploys and is
coming up more and more as scale goes up. Gary's point that we just added more
reasons to go to hbase:meta means we are making a bad situation worse. Needs
addressing. No work done on this though and won't have it block 2.0.0 release.
Downing it from blocker to critical in meantime.
> 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
(v7.6.3#76005)
