Uploaded image for project: 'Apache Ozone'
  1. Apache Ozone
  2. HDDS-505 OzoneManager HA
  3. HDDS-1319

In OM HA InitiateMultipartUpload call Should happen only leader OM

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: OM HA, Ozone Manager
    • Labels:
      None

      Description

      In OM HA, currently, when initiate multipart upload is called, in applyTransaction() on all OM nodes, it generates a multipartUploadID. So, each OM generates a new multipartUploadID. But the response we give to the client is multipartUploadID generated from OM leader node.

       

      Because this is the same multipartUploadID used during openKey and commitKey. (This will be sent from client who is creating this multipart upload for a key).

       

      To solve this issue, we take similar approach of openKey, where multipartUploadID will be generated in startTransaction and the same should be sent to all OM's. So that during applyTransaction all OM's will have the same multipartUploadID.

       

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                bharat Bharat Viswanadham
                Reporter:
                bharat Bharat Viswanadham
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: