Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.2.0
    • Component/s: None
    • Labels:
      None

      Description

      Big data workloads frequently exceed the AzureBlobFS max ingress and egress limits (https://docs.microsoft.com/en-us/azure/storage/common/storage-scalability-targets). For example, the max ingress limit for a GRS account in the United States is currently 10 Gbps. When the limit is exceeded, the AzureBlobFS service fails a percentage of incoming requests, and this causes the client to initiate the retry policy. The retry policy delays requests by sleeping, but the sleep duration is independent of the client throughput and account limit. This results in low throughput, due to the high number of failed requests and thrashing causes by the retry policy.

      To fix this, we introduce a client-side throttle which minimizes failed requests and maximizes throughput. 

        Attachments

        1. HADOOP-15703-HADOOP-15407-001.patch
          32 kB
          Sneha Varma
        2. HADOOP-15703-HADOOP-15407-002.patch
          40 kB
          Thomas Marqardt
        3. HADOOP-15703-HADOOP-15407-003.patch
          3 kB
          Thomas Marqardt
        4. HADOOP-15703-HADOOP-15407-004.patch
          3 kB
          Thomas Marqardt

          Activity

            People

            • Assignee:
              tmarquardt Thomas Marqardt
              Reporter:
              snehavarma Sneha Varma
            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: