Geo: Improve chances of the first stage of the pipeline being accelerated by Geo secondary
Release notes
Problem to solve
Geo accelerates CI runners by allowing them to clone from secondary sites. However, the clone for the first stage of the pipeline is almost always proxied to the primary site. This is because the verification of the replicated changes (such as pipeline ref) has not been completed by the time the first stage of the pipeline is executed. Typically it takes about 90 seconds for the verification to complete on a lightly loaded deployment.
This issue is a follow on from discussions had here
Proposal
Ensure that the clone for the first stage of the pipeline is guaranteed or has a higher chance of being served from a secondary site.
Some options that have been discussed:
- The decision to proxy the request to the primary is not made on the status of verification but instead on the status of replication
- Delay the clone request at the secondary site until replication and verification is complete.