chore: gdb regions - #1266
Open
karenc-bq wants to merge 1 commit into
Open
Conversation
karenc-bq
force-pushed
the
chore/gdb-aws-region
branch
from
August 6, 2026 01:25
f849461 to
5ef1cc3
Compare
karenc-bq
force-pushed
the
chore/gdb-aws-region
branch
from
August 6, 2026 01:53
5ef1cc3 to
fca73dc
Compare
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.
Summary
gdb_accessible_regions)monitoring_connection_priority,gdb_monitoring_connection_priority)Description
GdbFailoverPlugin— failover candidates are filtered by accessible regions. In strict-writer mode, failover fails fast if the writer is in a non-accessible region.GdbReadWriteSplittingPlugin— writer connections to non-accessible regions are rejected. Reader candidates are filtered before applying home-region restrictions.GlobalAuroraTopologyMonitor— topology monitoring host workers skip non-accessible regions. The initial host's region is validated and the monitor fails fast if it is not accessible. When the writer is unreachable, the monitor exits panic mode by adopting harvested reader connections (stable-reader-topology consensus).AuroraInitialConnectionStrategyPlugin— host candidates are filtered by accessible regions before strategy-based selection. Filtering is delegated to the dialect viaDatabaseDialect.filter_available_hosts(hosts, accessible_regions), which is a no-op for non-Global dialects and an actual region filter forGlobalAuroraMysqlDialectandGlobalAuroraPgDialect.Both
GdbFailoverPluginandGdbReadWriteSplittingPluginvalidate at initialization that the configured home region is included in the accessible regions list when both are specified.New configuration parameter
monitoring_connection_priorityComma-separated ordered list of priorities for the topology monitoring connection:
strict-writer,strict-reader,writer-or-reader. Default isstrict-writer. The monitor accepts any connection initially and asynchronously upgrades to a higher-priority host without blocking the monitoring loop.New configuration parameter
gdb_monitoring_connection_priorityGDB-specific extension supporting region-aware values:
strict-writer-primary,strict-reader-primary,strict-reader-secondary,strict-writer-<region>,strict-reader-<region>, and plain<region>(any host in that region). Default isstrict-writer-primary.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.