Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • O OS Core Lib Azure
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 9
    • Issues 9
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 7
    • Merge requests 7
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Open Subsurface Data Universe SoftwareOpen Subsurface Data Universe Software
  • Platform
  • System
  • Lib
  • cloud
  • azure
  • OS Core Lib Azure
  • Merge requests
  • !155

throw explicit 503 when server is busy to process BlobStorage request so client can retry

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged neelesh thakur requested to merge handle-blob-503 into master Oct 06, 2021
  • Overview 3
  • Commits 3
  • Pipelines 6
  • Changes 3

We see Storage API starts to responds with 500 when system is under heavy ingestion for very few requests. On closer look, we found that BlobStorage is throttled and underlaying error message is following:

AppException(error=AppError(code=500, reason=Failed to read specified blob, message=Status code 503, "ServerBusyThe server is busy._RequestId:82895e12-701e-0066-26d3-b568b7000000_Time:2021-09-30T08:13:49.5116925Z", errors=null, debuggingInfo=null, originalException=com.azure.storage.blob.models.BlobStorageException: Status code 503, "ServerBusyThe server is busy.

RequestId:82895e12-701e-0066-26d3-b568b7000000

Time:2021-09-30T08:13:49.5116925Z"), originalException=com.azure.storage.blob.models.BlobStorageException: Status code 503, "ServerBusyThe server is busy.

RequestId:82895e12-701e-0066-26d3-b568b7000000

Time:2021-09-30T08:13:49.5116925Z")

image

With this change, client can retry based of response code.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: handle-blob-503