Repository navigation
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
b/568415381
Problem
The Batch region only comes from
batch.yaml, which ships with the release. Changing it needs a prod deploy, and every deploy recreates all long-lived VMs. During a stockout that's exactly what we can't do, since some of those VMs may not come back.Solution
New feature flag,
batch_alternative_region:string_value: the region, e.g.us-east1.value: share of new Batch jobs to send there, from 0 to 1. Required.When it's enabled,
_get_subconfigsends that share of jobs to the region. The network and subnetwork come from a newalternative_regionsection inbatch.yaml, with{region}filled in. The region is load-checked like the others. If it's full or the section is missing, jobs wait. There's no automatic fallback. The flag is cached for a minute.With the flag off (the default), nothing changes.
Config side: go/clusterfuzz-config-pr/412
Validation
TODO