Details
-
Improvement
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
None
-
None
-
None
Description
We should not need to take a table offline to update HCD or HTD.
One option for that is putting HTDs and HCDs up into ZK, with mirror on disk catalog tables to be used only for cold init scenarios, as discussed on IRC. In this scheme, regionservers hosting regions of a table would watch permanent nodes in ZK associated with that table for schema updates and take appropriate actions out of the watcher. In effect, schema updates become another item in the ToDo list.
/hbase/tables/<table-name>/schema
Must be associated with a write locking scheme also handled with ZK primitives to avoid situations where one concurrent update clobbers another.
Attachments
Attachments
Issue Links
- blocks
-
HBASE-1636 disable and drop of table is flakey still
- Closed
- breaks
-
HBASE-5359 Alter in the shell can be too quick and return before the table is altered
- Closed
- is part of
-
HBASE-1816 Master rewrite
- Closed
- is related to
-
HBASE-4213 Support for fault tolerant, instant schema updates with out master's intervention (i.e with out enable/disable and bulk assign/unassign) through ZK.
- Closed
- relates to
-
HBASE-1728 Column family scoping and cluster identification
- Closed
-
HBASE-4729 Clash between region unassign and splitting kills the master
- Closed