Uploaded image for project: 'Apache Ozone'
  1. Apache Ozone
  2. HDDS-1672 Improve locking in OzoneManager
  3. HDDS-1727

Use generation of resourceName for locks in OzoneManagerLock

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 0.4.1
    • None
    • Done

    Description

      In this Jira, we shall use generate Resourcename from actual resource names like volume/bucket/user/key inside OzoneManagerLock. In this way, users using these locking API's no need to worry of calling these additional API of generateResourceName in OzoneManagerLockUtil. And this also reduces code during acquiring locks in OM operations.

      Attachments

        Issue Links

          relates to

          Sub-task - The sub-task of the issue HDDS-1723 Create new OzoneManagerLock class

          • Major - Major loss of function.
          • Resolved
          links to

          Web Link GitHub Pull Request #1014

          Activity

            People

              bharat Bharat Viswanadham
              bharat Bharat Viswanadham
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 1h 40m
                  1h 40m