[
https://issues.apache.org/jira/browse/HBASE-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-7767:
-------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
Release Note: Keeps table enabled/disabled state in HDFS rather than up in
ZooKeeper. Auto-migrates any existing zk state.
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Pushed to master. Thanks for the excellent patch [~octo47].
The findbugs are from elsewhere and the tests are flakies we should address
elsewhere.
Since this auto-migrates, we should bring this back for 1.0 I'd say. Let me
make myself an issue against 0.99 to test it actually works before committing
to 0.99.
Is replication state the only permanent data now left in zk?
> Get rid of ZKTable, and table enable/disable state in ZK
> ---------------------------------------------------------
>
> Key: HBASE-7767
> URL: https://issues.apache.org/jira/browse/HBASE-7767
> Project: HBase
> Issue Type: Sub-task
> Components: Zookeeper
> Affects Versions: 2.0.0
> Reporter: Enis Soztutar
> Assignee: Andrey Stepachev
> Fix For: 2.0.0
>
> Attachments:
> 0001-HBASE-7767-Get-rid-of-ZKTable-and-table-enable-disab.patch,
> 0001-rebase.patch, 7767v2.txt, HBASE-7767.patch, HBASE-7767.patch,
> HBASE-7767.patch, HBASE-7767.patch, HBASE-7767.patch, HBASE-7767.patch,
> HBASE-7767.patch, HBASE-7767.patch, HBASE-7767.patch, HBASE-7767.patch,
> HBASE-7767.patch, HBASE-7767.patch, HBASE-7767.patch
>
>
> As discussed table state in zookeeper for enable/disable state breaks our
> zookeeper contract. It is also very intrusive, used from the client side,
> master and region servers. We should get rid of it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
