"The mirroring feature is not available." is written to the application log of non datacentre instances.

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Low
    • 5.3.0
    • Affects Version/s: 4.14.4
    • Component/s: None
    • None
    • Severity 3 - Minor
    • 32

      Non data centre Bitbucket Server instances will log the below at WARN level whenever someone hovers over the clone button in a repository:

      The mirroring feature is not available.

      When user hovers over the clone button, the frontend makes a request to the /rest/mirroring/latest/repos/$REPO_ID/mirrors REST endpoint.

      Stop doing this as it is unnecessary and adds noise to applications logs.

      Steps to fix:

      • Stop the frontend from making the request on non-DC instances
      • The message shouldn't be logged at WARN level

      Workaround

      One workaround is to set the log level for com.atlassian.bitbucket.internal.mirroring.upstream.DefaultSmartMirroringFeature to ERROR. Note care must be taken to only set this log level to ERROR for this class otherwise important logging could be lost. 

       

            Assignee:
            Frank Doherty
            Reporter:
            rikf
            Votes:
            5 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: