[
https://issues.apache.org/jira/browse/HBASE-10161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13850108#comment-13850108
]
Anoop Sam John commented on HBASE-10161:
----------------------------------------
bq.We don't need to check in postOpen if the region is in recovery?
Yes we have to... Oh I can see that change in my eclipse code base but in this
patch.. I think I have attached wrongly the 1st patch I produced with out this
change.. Will do that in the next patch.
bq.Don't we have to deny everything until initialized?
What I was thinking is I will make this table also as write on replay false.
(Again missing this also in this patch because of the above reason :) )
Any read request to the table will fail with RegionInRecoveryException. The
permission checking will rely on cache and so those ops also might fail (?)
In other patch for visibility the write ops I have checked as we were using the
ordinal no also which might not be initialized.
What all ops u feel we need to check for init. The admin ops on acl table?
> [AccessController] Tolerate regions in recovery
> -----------------------------------------------
>
> Key: HBASE-10161
> URL: https://issues.apache.org/jira/browse/HBASE-10161
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.96.0
> Reporter: Andrew Purtell
> Assignee: Anoop Sam John
> Priority: Blocker
> Fix For: 0.98.0, 0.96.2, 0.99.0
>
> Attachments: HBASE-10161.patch
>
>
> AccessController fixes for the issue also affecting VisibilityController
> described on HBASE-10148. Coprocessors that initialize in postOpen upcalls
> must check if the region is still in recovery and defer initialization until
> recovery is complete. We need to add a new CP hook for post recovery upcalls
> and modify existing CPs to defer initialization until this new hook as needed.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
