Adminstration guidelines to migrate to postgresql#103
Conversation
sghosh23
changed the title
| - Conversation codes | ||
| - Team features | ||
|
|
||
| After the migration is complete, PostgreSQL becomes the authoritative store for the migrated domains. |
There was a problem hiding this comment.
I'm not sure i would have used data domains as the term here; when you say migrated domains, people think DNS.
|
|
||
| The `cassandra-migrations` job only prepares schema and metadata. It does not copy conversation data from Cassandra into PostgreSQL. The data copy is performed by `background-worker`. | ||
|
|
||
| ## PostgreSQL Connection Budget |
There was a problem hiding this comment.
Move this into a dedicated document; it is general guidance, not migration related.
There was a problem hiding this comment.
it's already moved to the dedicated domain, what we have here is the awareness of using the connection budget and link to that dedicated document
|
|
||
| - `galley` should restart cleanly. | ||
| - New writes for that domain should be written to both Cassandra and PostgreSQL. | ||
| - No backfill should run yet. |
There was a problem hiding this comment.
Define backfill for the person running through this document.
| - `error occurred` | ||
| - `estimatedRows` | ||
|
|
||
| Useful Prometheus metrics: |
There was a problem hiding this comment.
We cannot assume they have metrics configured; leave a note pointing to how to pull metrics manually, for those who don't have it (read: everyone!)
|
|
||
| After this rollout, the selected domain reads from PostgreSQL only. | ||
|
|
||
| ## Recommended Domain Order |
There was a problem hiding this comment.
you should recommend the order before giving the instructions.
Co-authored-by: Julia Longtin <julia.longtin@gmail.com>
2 participants
Change type
Basic information
Testing
Tracking