Geo - Secondary tries to download a file indefinitely when sync object storage is enabled but object storage is disabled for data type
Summary
Geo secondary nodes try to download a file indefinitely when syncing object storage is enabled, but the object storage is disabled for data type on the secondary node. The same bug happens when we try to remove the file using the Geo::FileRegistryRemovalWorker
.
Steps to reproduce
-
Enable Object Storage for LFS Objects only on the primary node
-
Enable
Allow this secondary node to replicate content on Object Storage
for the secondary node -
Push a new LFS file to a repository on the primary node
-
Visit the
Admin Area
->Monitoring
->Background Jobs
->Retries
What is the expected correct behavior?
The Geo secondary node should skip the transfer when it is not allowed to replicate content on Object Storage or is not configured to store the data type on Object Storage.