Summary

With at least one Git repository migrated to Mesh, in rare cases of issues with underlying infrastructure when a large number of operations are going on on the Mesh nodes, repository settings may show only a part of the remote Mesh nodes containing the Git repository.

Symptoms observed may be similar to these:

• The repository settings page shows only two remote Mesh nodes containing the repository.

• The remaining nodes may show higher traffic than normal. There may be one or more other nodes.

• Only two replicas are shown when calling REST API

  curl -X GET --location "{{base_url}}/rest/ui/latest/admin/git/mesh/troubleshooting/projects/{{projectId}}/repos/{{repoSlug}}/replicas" \
      -H "Accept: application/json" \
      --basic --user {{user}}:{{password}}

Environment

Bitbucket Data Center 8.x and newer

Remote Mesh 1.0.0 and newer

At least one of the repositories has been migrated to Mesh nodes.

Solution

The remote Mesh system should automatically detect that, for one of the Git repositories, less than the replication factor remote Mesh nodes contain that repository. It will then pick one of the Mesh nodes that does not have the repository and assign the repository to it. That “new” node will then attempt to automatically repair the repository, which should bring the number of remote Mesh nodes holding the repository up to the “replication factor”.