Skip to content
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

Add blog post about Postgres downtime #347

Merged
merged 6 commits into from
Feb 4, 2025
Merged

Add blog post about Postgres downtime #347

merged 6 commits into from
Feb 4, 2025

Conversation

ericholscher
Copy link
Member

@ericholscher ericholscher commented Jan 30, 2025

@ericholscher ericholscher requested a review from a team as a code owner January 30, 2025 23:50
@humitos
Copy link
Member

humitos commented Feb 3, 2025

Mostly copied from blog.readthedocs.com/rtd-business-downtime-feb-5

2021 was our last scheduled downtime!? Wow! 🤯

Copy link
Member

@humitos humitos left a comment

Choose a reason for hiding this comment

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

Looks good with small adjustments.

content/posts/aws-rds-upgrade.md Outdated Show resolved Hide resolved
content/posts/aws-rds-upgrade.md Outdated Show resolved Hide resolved
This will impact both **Read the Docs Community** and **Read the Docs for Business**.
We expect the downtime to only last for 15-30 minutes, but we are scheduling a longer window to account for any unforeseen issues.

During this maintenance window, documentation will continue to be online but new documentation builds will not trigger and the Read the Docs dashboard will be unavailable.
Copy link
Member

Choose a reason for hiding this comment

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

documentation will continue to be online

Is this true? Are we still being able to read data from Postgres? Otherwise, only the documentation cached by CF will be available, right?

Copy link
Contributor

Choose a reason for hiding this comment

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

I believe last time we did this we promoted the read replica so that at least read-only database operations worked.

If we aren't planning on this for this migration, private documentation will not be available.

Copy link
Member Author

Choose a reason for hiding this comment

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

I think we switched the queries over to the read-only DB with a DB router, IIRC.

Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah, likely. I think that was when we had a more complex database router configuration too, the replica might have been the primary database used for auth.

We have a few options we can pick from, worst case we might need a release prior to the window

Copy link
Member Author

@ericholscher ericholscher Feb 4, 2025

Choose a reason for hiding this comment

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

I noted that public docs will continue to work. I don't think we want to do a bunch of work here for a small maint. window.

@ericholscher ericholscher merged commit 7fdbae6 into main Feb 4, 2025
4 checks passed
@ericholscher ericholscher deleted the postgres-maint branch February 4, 2025 19:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants