[
https://issues.apache.org/jira/browse/HDDS-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham updated HDDS-1723:
-------------------------------------
Issue Type: Sub-task (was: Improvement)
Parent: HDDS-1672
> Create new OzoneManagerLock class
> ---------------------------------
>
> Key: HDDS-1723
> URL: https://issues.apache.org/jira/browse/HDDS-1723
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Components: Ozone Manager
> Reporter: Bharat Viswanadham
> Assignee: Bharat Viswanadham
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.4.1
>
> Time Spent: 6h 20m
> Remaining Estimate: 0h
>
> This Jira is to use bit manipulation, instead of hashmap in OzoneManager lock
> logic. And also this Jira follows the locking order based on the document
> attached to HDDS-1672 jira.
> This Jira is created based on [~anu] comment during review of HDDS-1672.
> Not a suggestion for this patch. But more of a question, should we just
> maintain a bitset here, and just flip that bit up and down to see if the lock
> is held. Or we can just maintain 32 bit integer, and we can easily find if a
> lock is held by Xoring with the correct mask. I feel that might be super
> efficient. [@nandakumar131|https://github.com/nandakumar131] . But as I said
> let us not do that in this patch.
>
> This Jira will add new class, integration of this new class into code will be
> done in a new jira.
> Clean up of old code also will be done in new jira.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
