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

Duo Zhang commented on HBASE-23103:
-----------------------------------

AsyncRpcRetryingCaller is the base class for retrying caller of normal 
read/write.

And for altering meta, I do not think keep the state transient can solve all 
the problems. It has inherent complexity. Master startup needs meta table 
online as we need to scan meta, and here want to disable meta. Even if we 
automatically make meta enabled, we may still hit problems, for example, the 
ModifyTableProcedure is only half done and assume that meta table is disabled, 
but after restarting, meta table is enabled, and the procedure can not 
continue...

As now, altering a table does not need to disable the table, I suggest we still 
keep meta always enabled, and add special logic to deal with meta table in 
ModifyTableProcedure, SplitTableRegionProcedure, MergeTableRegionsProcedure, 
etc.

Thanks.

> Survey incidence of table state queries
> ---------------------------------------
>
>                 Key: HBASE-23103
>                 URL: https://issues.apache.org/jira/browse/HBASE-23103
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Michael Stack
>            Priority: Blocker
>             Fix For: 3.0.0
>
>
> 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to