hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Laxman (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (HBASE-6186) Assure thread safety
Date Thu, 07 Jun 2012 21:42:23 GMT

     [ https://issues.apache.org/jira/browse/HBASE-6186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Laxman reassigned HBASE-6186:

    Assignee: Laxman
> Assure thread safety
> --------------------
>                 Key: HBASE-6186
>                 URL: https://issues.apache.org/jira/browse/HBASE-6186
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Andrew Purtell
>            Assignee: Laxman
> Check data structures for necessary thread safety.
> One known issue is as follows:
> In TableAuthManager, we need to deal with concurrent grants and revokes now that ADMIN
permission can be delegated to perhaps multiple users.
> Consider using a ReadWriteLock to protect for update. The current data structure is an
array multimap. It is also possible to obtain a synchronized multimap from Guava with Multimaps#synchronizedListMultimap
but by far the most common access is read access, and concurrent read access is fine.

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


View raw message