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

Enable Ref advertisement caching by default on mirrors

    XMLWordPrintable

    Details

    • Type: Suggestion
    • Status: Closed (View Workflow)
    • Resolution: Fixed
    • Fix Version/s: 5.15.0
    • Component/s: None
    • Labels:
      None
    • Feedback Policy:
      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

      Problem Definition

      Mirrors can receive many concurrent ref advertisement requests (mainly by CI/CD tools).
      These requests will lead to scm tickets being consumed very quickly and operations to being queued.
      In some extreme cases, this could even lead to operations not being performed at all when the timeouts are hit.

      Suggested Solution

      Enable the "Ref advertisement caching" by default on mirrors

      Workaround

      In the interim, enable the ref advertisement cache by adding the following to the bitbucket.properties file for each mirror:

      plugin.bitbucket-scm-cache.refs.enabled=true
      

      Note
      no plugins can be installed on mirrors so the refs will always be in the expected status in the caches because. There is no risk that a plugin will manipulate the refs without the caching plugin detecting these changes.

      Note 2
      It is not possible to set or check the status of the ref cache by using REST API endpoints on the mirror.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              mheemskerk Michael Heemskerk
              Reporter:
              ccurti Caterina Curti
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: