Uploaded image for project: 'Apache Ozone'
  1. Apache Ozone
  2. HDDS-4944 Multi-Tenant Support in Ozone
  3. HDDS-6701

[Multi-Tenant] Add proper locking between Ranger background sync service and tenant requests; bug fixes

Attach filesAttach ScreenshotVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • HDDS-4944
    • None

    Description

      1. This is a follow-up jira to HDDS-6371 to implement proper locking.
      2. Need two versions of createTenantAccess: InAuthorizer and InDB (updates cache)
      3. Implement tenant delete Ranger call
      4. Better Ranger error handling (e.g. throw easily identifiable exceptions; check HTTP response code from the Ranger endpoint)

      Attachments

        Issue Links

        incorporates

        Sub-task - The sub-task of the issue HDDS-6691 [MultiTenancy] User get-secret throws USER_MISMATCH

        • Critical - Crashes, loss of data, severe memory leak.
        • Resolved
        links to

        Web Link GitHub Pull Request #3450

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            smeng Siyao Meng
            smeng Siyao Meng
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment