[
https://issues.apache.org/jira/browse/HBASE-16060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16359099#comment-16359099
]
stack commented on HBASE-16060:
-------------------------------
Ok. First set up cluster with hbase-1 data. Shut it down. Start hbase-2 over
hbase-1 data. In logs I see these messages:
....
2018-02-09 15:28:40,980 INFO [master/ve0524:16000]
master.MirroringTableStateManager: Migrating table state from zookeeper to
hbase:meta; tableName=enabled2, state=ENABLED
2018-02-09 15:28:41,166 INFO [master/ve0524:16000] hbase.MetaTableAccessor:
Updated table enabled2 state to ENABLED in META
2018-02-09 15:28:41,177 INFO [master/ve0524:16000]
master.MirroringTableStateManager: Migrating table state from zookeeper to
hbase:meta; tableName=hbase:namespace, state=ENABLED
2018-02-09 15:28:41,189 INFO [master/ve0524:16000] hbase.MetaTableAccessor:
Updated table hbase:namespace state to ENABLED in META
2018-02-09 15:28:41,200 INFO [master/ve0524:16000]
master.MirroringTableStateManager: Purged table state entry for table not in
hbase:meta: disable
2018-02-09 15:28:41,210 INFO [master/ve0524:16000]
master.MirroringTableStateManager: Migrating table state from zookeeper to
hbase:meta; tableName=disabled, state=DISABLED
...
so migration of table state from zk to hbase:meta seems to work. Restart and no
messages (though we are doing the work to see if we need to migrate states... ).
> 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
> Assignee: stack
> Priority: Blocker
> Fix For: 2.0.0-beta-2
>
> Attachments:
> 0002-HBASE-16060-1.x-clients-cannot-access-table-state-ta.patch,
> HBASE-16060.branch-2.001.patch
>
>
> 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
(v7.6.3#76005)
