You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-dev@hadoop.apache.org by "Bharat Viswanadham (JIRA)" <ji...@apache.org> on 2019/06/22 00:06:00 UTC

[jira] [Created] (HDDS-1723) Create new OzoneManagerLock class

Bharat Viswanadham created HDDS-1723:
----------------------------------------

             Summary: Create new OzoneManagerLock class
                 Key: HDDS-1723
                 URL: https://issues.apache.org/jira/browse/HDDS-1723
             Project: Hadoop Distributed Data Store
          Issue Type: Bug
            Reporter: Bharat Viswanadham
            Assignee: Bharat Viswanadham


This Jira is to user bit manipulation, instead of hashmap in OzoneManager lock logic.

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-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org