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-16025) Cache table state to reduce load on META
Date Sat, 03 Jun 2017 17:51:04 GMT

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

stack commented on HBASE-16025:

AMv2 has table state in hbase:meta so I presume we have this issue still; to be confirmed.
We should do as Gary suggests anyways.

> 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: Blocker
>             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

This message was sent by Atlassian JIRA

View raw message