After upgrading to 5.16.x, the application logs contain a git-upload-pack message.
This appears to be a manifestation of https://jira.atlassian.com/browse/BSERV-11330 but customers that have upgraded to 5.16.x still see the warnings.
Apart from this warning message in the logs, there don't seem to be any issues
It can be reproduced intermittently by performing multiple concurrent git fetches of the same repository at the same time over the ssh protocol and when it's either a cache:miss or a cache:bypass (ref advertisement cache is not enabled).
No warning message should appear in the application logs.
The below exception is thrown in the atlassian-bitbucket.log file:
These can be turned off using a REST API call (without the need of a restart), but users will lose the visibility that they have been turned off and miss new warnings in the future. For this reason our recommendation is to add the following to the bitbucket.properties file and restart or let the next restart apply the new setting:
This line is increasing the log level from WARN to ERROR.
The API workaround only applies until Bitbucket is stopped, upon restart the values in the bitbucket.properties or the defaults apply.
This is the endpoint to use for changing the log level to ERROR: