Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-9725

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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 5.3.0
    • 4.14.4
    • None
    • None

      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. 

       

            [BSERV-9725] "The mirroring feature is not available." is written to the application log of non datacentre instances.

            Frank Doherty added a comment -
            • Changed the log message level to debug instead of warn
            • Added a check for mirroring to the client resource

            Frank Doherty added a comment - Changed the log message level to debug instead of warn Added a check for mirroring to the client resource

            Brent P added a comment -

            This happens when you hover over the clone dialog on a non-DC instance.

            Discussion at triage:

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

            Brent P added a comment - This happens when you hover over the clone dialog on a non-DC instance. Discussion at triage: We should stop the frontend from making the request on non-DC instances. The message shouldn't be logged at WARN level

              fdoherty@atlassian.com Frank Doherty
              rfriend rikf
              Affected customers:
              5 This affects my team
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: