Geo: High rate of "Cannot obtain an exclusive lease" messages

On the Geo secondary, we're seeing a lot of "Cannot obtain an exclusive lease. There must be another instance already in execution" messages:

image

It looks like the main culprit is reported by Geo::RepositorySyncService, followed by Geo::RepositoryShardSyncWorker.

If you look at Kibana by project ID, it seems that the same projects may be scheduled in close proximity:

image