hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16060) 1.x clients cannot access table state talking to 2.0 cluster
Date Mon, 20 Jun 2016 18:50:58 GMT

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

Enis Soztutar commented on HBASE-16060:

bq. The Semantic Versioning, we say in major release (2.0), Client-Server wire Compatibility
is N.
The guide just says that we are not cornering ourselves and we do not have to have wire compat
between major versions. That does not mean that we won't work through achieving this for the
convenience of users and cluster operators. 

bq. How the rolling upgrade going to required?
This has been discussed before on some other settings, but maybe time to start a dev thread
and formalize on it. Both my and [~mbertozzi]'s slides on hbasecon was talking about the fact
that 0.94 -> 0.96 singularity was awful for users and we do not want to make the users
suffer through it once more for 1.x -> 2.0. 1.x to 2.0 wire compat is achievable with some
effort today, and I don't see any reason why we should not shoot for it. 

> 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
>             Fix For: 2.0.0
> 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

View raw message