[
https://issues.apache.org/jira/browse/HBASE-6096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290925#comment-13290925
]
Laxman commented on HBASE-6096:
-------------------------------
bq. So for some short period after a grant, access may be denied; and,
conversely, for some short period after a revoke, access may be allowed.
I agree with you on this Andy. But this is not my concern. I could have provide
context.
bq. Maybe you can provide more context?
In TableAuthManager, we may need to maintain thread-safe data structures.
What I meant by concurrency was, when we execute access control
operations(grant, revoke) and other user operation (scan, get, put) some calls
may fail. Reasons for failure
1) access control operations updates USER_CACHE & GROUP_CACHE
2) user operation reads from USER_CACHE & GROUP_CACHE.
And these data structures [ArrayListMultimap] are not thread-safe.
http://google-collections.googlecode.com/svn/trunk/javadoc/com/google/common/collect/ArrayListMultimap.html
Please correct me if I'm missing something here.
> AccessController v2
> -------------------
>
> Key: HBASE-6096
> URL: https://issues.apache.org/jira/browse/HBASE-6096
> Project: HBase
> Issue Type: Umbrella
> Components: security
> Affects Versions: 0.96.0, 0.94.1
> Reporter: Andrew Purtell
>
> Umbrella issue for iteration on the initial AccessController drop.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
