Conversation
RC: Seamless endpoint migration phase A
andy-stark-redis
left a comment
andy-stark-redis
left a comment
There was a problem hiding this comment.
Embed paths need to be fixed but otherwise LGTM.
|
|
||
| ### Dynamic endpoints | ||
|
|
||
| As of {{RELEASE DATE}}, Redis Cloud now generates dynamic endpoints for all databases. Databases created before {{RELEASE DATE}} can still view both static endpoints and dynamic endpoints. Static endpoints will still work at this time, but they may be deprecated in the future. |
There was a problem hiding this comment.
Just checking that the {{ RELEASE DATE}} still isn't known yet?
There was a problem hiding this comment.
current eta is March 22
Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com>
kaitlynmichael
left a comment
kaitlynmichael
left a comment
There was a problem hiding this comment.
Didn't get through it all yet, but here's a few small things.
Co-authored-by: Kaitlyn Michael <76962844+kaitlynmichael@users.noreply.github.com>
andy-stark-redis
left a comment
andy-stark-redis
left a comment
There was a problem hiding this comment.
A few minor style suggestions, otherwise LGTM.
|
|
||
| ### Dynamic endpoints | ||
|
|
||
| As of {{RELEASE DATE}}, Redis Cloud now generates dynamic endpoints for all databases. Databases created before {{RELEASE DATE}} can still view both static endpoints and dynamic endpoints. Static endpoints will still work at this time, but they may be deprecated in the future. |
There was a problem hiding this comment.
current eta is March 22
|
|
||
| ### Dynamic endpoints | ||
|
|
||
| As of {{RELEASE DATE}}, Redis Cloud now generates dynamic endpoints for all databases. Databases created before {{RELEASE DATE}} can still view both static endpoints and dynamic endpoints. Static endpoints will still work at this time, but they may be deprecated in the future. |
There was a problem hiding this comment.
I think we need a section in the docs on "Dynamic endpoints" (maybe in the configuration page, or connectivity?). That would explain a few sentences what Dynamic endpoints are and that you can redirect endpoints, alias of the dB endpoint, bla bla bla.
And link it from here and from other places in the docs
Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com>
🛡️ Jit Security Scan Results
✅ No security findings were detected in this PR
Security scan by Jit
|
| To illustrate, suppose you want to migrate a 1 GB source database without replication to a target database with replication enabled. Here, the target database memory limit should be at least 2.5 GB to avoid data loss. | ||
|
|
||
| Once the databases are synced, you can disable Active-Passive for the target database. Before doing so, however, verify that apps and other connections have switched to the target database; otherwise, you may lose data. | ||
|
|
There was a problem hiding this comment.
Here I want to add a note regarding the API. I'll describe the process and you will do your magic to make it clear and put here where you think:)
- In the UI, the process is as you described. You just search for your DB in the search
- Using the API is different. Because the Dynamic endpoint can move, the user needs to give us the cluster endpoint and not dynamic one. In the UI we don't need to do adjustments because we just choose the actual DB.. not the endpoint
- What we did:
- We exposed a new attribute in the API on the GET DB call: replicaAsSourceEndpoints
- So the customer will need to use those endpoints if they want to set the replica of the program programmatically.
There was a problem hiding this comment.
We should definitely put this in the API docs. I'll work on adding this to the user docs later.
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
| 1. [Create a new database in Redis Cloud Pro](#create-rcp) with the right specifications to be able to migrate your database. | ||
|
|
||
| 1. [Migrate your Essentials database](#migrate-database) to your new Redis Cloud Pro database. | ||
| 1. [Migrate the data in your Essentials database](#migrate-database) to your new Redis Cloud Pro database. |
There was a problem hiding this comment.
Broken anchor link to renamed heading
Medium Severity
The link at line 28 points to #migrate-database, but the heading it references was renamed from ### Migrate database to ### Migrate data, which generates the auto-anchor #migrate-data. This results in a broken in-page navigation link.
Additional Locations (1)
| 1. [Migrate your Essentials database](#migrate-database) to your new Redis Cloud Pro database. | ||
| 1. [Migrate the data in your Essentials database](#migrate-database) to your new Redis Cloud Pro database. | ||
|
|
||
| 1. [Migrate your endpoints](#migrate-endpoints) to your new Redis Cloud Pro database. |
There was a problem hiding this comment.
Anchor #migrate-endpoints references nonexistent heading
Medium Severity
The new link at line 30 points to #migrate-endpoints, but the corresponding section heading at line 91 is ### Redirect database endpoints, which auto-generates the anchor #redirect-database-endpoints. No heading with anchor #migrate-endpoints exists anywhere on this page, so the link is broken.
Additional Locations (1)
4 participants
Note
Low Risk
Docs-only update that adds and reorganizes guidance around dynamic endpoints and endpoint redirection; main risk is confusing or incorrect instructions/links affecting customer migrations.
Overview
Adds new Redis Cloud docs for dynamic database endpoints and endpoint redirection, including a new
redirect-endpointsguide and March 2026 changelog entries describing rollout, compatibility checks, a 5‑minute traffic stop during redirection, and 24‑hour revert behavior.Updates connection and migration guidance to distinguish legacy static vs dynamic endpoints, recommend migrating to dynamic endpoints, and add “next steps” to redirect endpoints after data migration (including Essentials→Pro upgrade flow changes such as matching port requirements).
Standardizes how to obtain the Prometheus endpoint by adding an
rc-get-prometheus-endpointembed and reusing it across Prometheus/New Relic/Dynatrace integration docs and themonitor-performancepage.Written by Cursor Bugbot for commit 12ca89a. This will update automatically on new commits. Configure here.