Skip to content

Commit

Permalink
docs/rfcs: add RFC for fast tenant migration/failover (#5029)
Browse files Browse the repository at this point in the history
## Problem

Currently we don't have a way to migrate tenants from one pageserver to
another without a risk of gap in availability.

## Summary of changes

This follows on from #4919

Migrating tenants between pageservers is essential to operating a
service
at scale, in several contexts:

1. Responding to a pageserver node failure by migrating tenants to other
pageservers
2. Balancing load and capacity across pageservers, for example when a
user expands their
   database and they need to migrate to a pageserver with more capacity.
3. Restarting pageservers for upgrades and maintenance

Currently, a tenant may migrated by attaching to a new node,
re-configuring endpoints to use the new node, and then later detaching
from the old node. This is safe once [generation
numbers](025-generation-numbers.md) are implemented, but does meet
our seamless/fast/efficient goals:

Co-authored-by: Christian Schwarz <christian@neon.tech>
  • Loading branch information
jcsp and problame committed Sep 28, 2023
1 parent 5fdc80d commit 6b4bb91
Showing 1 changed file with 599 additions and 0 deletions.
Loading

1 comment on commit 6b4bb91

@github-actions
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2588 tests run: 2465 passed, 0 failed, 123 skipped (full report)


Flaky tests (1)

Postgres 14

  • test_get_tenant_size_with_multiple_branches: release

Code coverage (full report)

  • functions: 53.0% (8041 of 15164 functions)
  • lines: 81.3% (47104 of 57938 lines)

The comment gets automatically updated with the latest test results
6b4bb91 at 2023-09-28T09:57:58.275Z :recycle:

Please sign in to comment.