Details
-
Sub-task
-
Status: Resolved
-
Blocker
-
Resolution: Information Provided
-
None
-
None
-
None
-
None
Description
Task that comes of parent issue. Parent makes it so we go via Master to figure state of a table. It is the authority and since the parent issues adds being able to enable/disable hbase:meta, table state is now in two places – in hbase:meta table... and elsewhere for the hbase:meta's state. Rather than have client go to two locations dependent on which table is being asked about, parent made it so we went to master. Parent allows that this puts more load on the Master. zhangduo brings up the valid concern that it might be too much or that dependent on the Master for state puts Master too much in-line with read/writes.
This issue is a survey to figure how much load and how much state-in-master could mess up inline read/writes.