Issue Summary

In mirror farms, there is significant log spamming at INFO level when the local repository ID does not exist in the specific mirror node, and the app attempts to clear the cache

Steps to Reproduce

1. Have a mirror farm with multiple nodes
2. The local IDs of repositories are not the same across mirror nodes (expected)

Expected Results

There is no logging such as 

2024-05-08 00:00:02,655 INFO  [topic-dispatcher:thread-1]  c.a.b.s.c.i.MeshScmCacheService Unable to clear cache as repository xxxx was not found.

Actual Results

There could be thousands of lines per day for each local repository ID that does not exist in the mirror node, making troubleshooting harder and misleading about a potential problem

The below exception is thrown in the atlassian-bitbucket-<DATE>.log file:

2024-05-08 00:00:02,655 INFO  [topic-dispatcher:thread-1]  c.a.b.s.c.i.MeshScmCacheService Unable to clear cache as repository xxxx was not found.

Workaround

For now, we can change the log level for the class:
Add the following properties to your ${BITBUCKET_HOME}/shared/bitbucket.properties on each farm node:

logging.logger.com.atlassian.bitbucket.scm.cache.internal.MeshScmCacheService=WARN