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-16060) 1.x clients cannot access table state talking to 2.0 cluster
Date Sat, 02 Sep 2017 00:12:04 GMT

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

stack commented on HBASE-16060:
-------------------------------

Running 1.0.1 shell against hbase2 HEAD list works but stuff like create, while they have
desired effect, they hang up waiting on state of table to show up in zk. Let me work on echo'ing
out to zk table states so hbase1 basic admin keeps working.

> 1.x clients cannot access table state talking to 2.0 cluster
> ------------------------------------------------------------
>
>                 Key: HBASE-16060
>                 URL: https://issues.apache.org/jira/browse/HBASE-16060
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Enis Soztutar
>            Priority: Blocker
>             Fix For: 2.0.0-alpha-3
>
>
> Since table state is migrated to meta instead of zk in 2.0, 1.x clients talking to 2.0
cluster cannot access the table state. This causes some weird behavior since from a client
perspective, {{Admin.isTableEnabled()}} and {{Admin.isTableDisabled()}} both return false.

> One option we can do is to add code in 1.x clients so that they can access the table
state in meta if needed. Otherwise, we can mirror the table state in zk (while keeping meta
as the source of truth) during 2.x lifecycle so that any 1.x client can still work correctly.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message