Uploaded image for project: 'Bitbucket Server'
  1. Bitbucket Server
  2. BSERV-10290

Default throttle.resource.scm-hosting.adaptive.limit.max too large

    XMLWordPrintable

Details

    • Suggestion
    • Status: Closed (View Workflow)
    • Resolution: Fixed
    • 5.6.0
    • None
    • None
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      In Bitbucket Server 4.11 adaptive throttling increased the maximum number of concurrent hosting operations concurrently runnable from:

      1.5*${scaling.concurrency}
      

      to

      12*${scaling.concurrency}
      

      This maximum appears to be too high and has caused problems such as:

      • Out of memory errors
      • Massive NFS performance degradation
      • Insufficient protection from adaptive throttling problems such as BSERVDEV-15333

      Workaround:
      In Bitbucket Server 5.6.0 and later the value will be set like so:

      throttle.resource.scm-hosting.adaptive.limit.max=4*${scaling.concurrency}
      

      For Bitbucket Server 4.11 to 5.5 the same effect can be achieved by adding the above line to the bitbucket.properties file and then rebooting the instance. It is recommend that any cluster installation consider setting this limit to avoid saturating the NFS server with a large number of concurrent requests.

      Attachments

        Issue Links

          Activity

            People

              behumphreys Ben Humphreys
              behumphreys Ben Humphreys
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: