feat(catalog): support for multiple catalog pods#2169
Open
pboyd wants to merge 2 commits intokubeflow:mainfrom
Open
feat(catalog): support for multiple catalog pods#2169pboyd wants to merge 2 commits intokubeflow:mainfrom
pboyd wants to merge 2 commits intokubeflow:mainfrom
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
pboyd
force-pushed
the
multi-catalog-pods
branch
3 times, most recently
from
bb1378d to
907a106
Compare
Enables horizontal scaling through PostgreSQL-based leader election that coordinates database writes across multiple pods. All pods serve read requests from in-memory data and database queries. The leader alone performs database writes: fetches models, writes updates, and cleans up orphaned data. Leadership transfers automatically when the leader fails. Implementation: - Leader election package using pglock for distributed locking - Loader split into StartReadOnly() and StartLeader() modes - Configuration: CATALOG_LEADER_LOCK_DURATION and CATALOG_LEADER_HEARTBEAT environment variables - Integration tests for multi-pod scenarios Signed-off-by: Paul Boyd <paul@pboyd.io>
Signed-off-by: Paul Boyd <paul@pboyd.io>
pboyd
force-pushed
the
multi-catalog-pods
branch
from
907a106 to
56a20d0
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
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.
Description
Enables horizontal scaling through PostgreSQL-based leader election that coordinates database writes across multiple pods.
All pods serve read requests from in-memory data and database queries. The leader alone performs database writes: fetches models, writes updates, and cleans up orphaned data. Leadership transfers automatically when the leader fails.
Implementation:
pglockfor distributed lockingStartReadOnly()andStartLeader()modesCATALOG_LEADER_LOCK_DURATIONandCATALOG_LEADER_HEARTBEATenvironment variablesHow Has This Been Tested?
In a local dev environment the deployment can be scaled up to multiple pods. Killing the leader or deleting the entry in the
locksis enough to trigger fail-over.Merge criteria:
DCOcheck)