New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sql/catalog: add region_liveness table #107903
Conversation
b3f6fe4
to
51b470f
Compare
Thank you for updating your pull request. Before a member of our team reviews your PR, I have some potential action items for you:
I was unable to automatically find a reviewer. You can try CCing one of the following members:
🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf. |
dcf4ca3
to
4c92325
Compare
34b8589
to
85f347d
Compare
db8ebf5
to
ee8733d
Compare
ee8733d
to
25559bd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great 💯
25559bd
to
57d718f
Compare
Previously, we had no way of tracking region liveness which could can be used to improve behaviour on region failures. To address this, this patch introduces the system.region_liveness table. Epic: CRDB-28158 Informs: cockroachdb#103727 Release note: None
e331c68
to
7d5efa7
Compare
7d5efa7
to
b156069
Compare
Previously, the region liveness table was only created for new clusters. This was inadequate because we need this table to be created for existing ones too. To address this, this patch adds a migration to create this table and clear its key space, since its been reused. Epic: CRDB-28158 Release note: None
b156069
to
5ecf019
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
bors r+ |
Build succeeded: |
This adds a new region_liveness table and a migration to create this table for existing clusters, allowing us to introduce the concept of region liveness in later PRs. This will allow certain system tables to be configured as SURVIVE REGION later on.
Epic: CRDB-28158