[Internal] Spec: Adds Gateway Account Property Flag for Dynamic Hedging Control#5719
Open
NaluTripician wants to merge 8 commits intomainfrom
Open
[Internal] Spec: Adds Gateway Account Property Flag for Dynamic Hedging Control#5719NaluTripician wants to merge 8 commits intomainfrom
NaluTripician wants to merge 8 commits intomainfrom
Conversation
…ng Control Introduces OpenSpec artifacts for a new Gateway-controlled account property (disableCrossRegionalHedging) that allows on-call engineers to dynamically disable hedging for PPAF-enabled accounts without rolling back PPAF. Artifacts: - proposal.md: Problem statement and motivation - design.md: Technical design with precedence rules and evaluation strategy - specs/gateway-hedging-override/spec.md: Detailed requirements and scenarios - tasks.md: Implementation checklist Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
NaluTripician
requested review from
FabianMeiswinkel,
Pilchie,
jeet1995,
kirankumarkolli,
kundadebdatta,
kushagraThapar,
sboshra and
xinlian12
as code owners
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
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
1 participant
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.
Summary
Introduces the OpenSpec specification artifacts for a Gateway-controlled account property flag (
disableCrossRegionalHedging) that enables on-call engineers to dynamically disable hedging for PPAF-enabled Cosmos DB accounts without rolling back PPAF entirely.Motivation
Production incidents have shown that implicit hedging of long-running queries on PPAF accounts can cause unexpected exceptions (e.g.,
ArgumentExceptionin CallStore). Rolling back PPAF to disable hedging is operationally expensive. This spec proposes a targeted, service-side escape hatch.Spec Artifacts
Key Design Decisions
bool?onAccountProperties(consistent withEnablePartitionLevelFailover)DocumentClient.UpdatePartitionLevelFailoverConfigWithAccountRefresh()— same callback that handles dynamic PPAF changestrueoverrides all hedging config (explicit + implicit)Precedence Rules
disableCrossRegionalHedging = true→ Hedging OFF (highest priority)falseor absent → existing rules apply (request-level → client-level → PPAF default)No Code Changes
This PR contains specification artifacts only — no SDK code changes are included. Implementation will follow in a separate PR.