You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit fc46b8c
Browse filesBrowse the repository at this point in the historyBrowse files
The relay Worker reads these variables and secrets when it is deployed. Alchemy does not redeploy the
144
+
Worker when only one of these values changes ([alchemy-run/alchemy#1831](https://github.com/alchemy-run/alchemy/issues/1831)),
145
+
so a push to `main` without relay code changes leaves the old value in place. After changing one, run
146
+
the **Deploy T3 Connect relay** workflow manually from `main` with **force** checked.
147
+
143
148
The account-scoped repository credentials are consumed by Alchemy while provisioning relay stages; they
144
149
are not bound into the relay Worker. The production deployment uses an Axiom personal access token,
145
150
so `AXIOM_ORG_ID` must accompany `AXIOM_TOKEN`. The `prod` stage owns the retained PlanetScale
@@ -163,18 +168,20 @@ because those builds register recovery and replace a deleted tunnel after wake.
163
168
1. Deploy the relay and migration with cleanup `off`.
164
169
2. Release the server build and confirm current hosts register recovery. Older hosts stay marked
165
170
legacy and are never candidates.
166
-
3. Set `dry-run`, deploy, and read the sweep counters (`scanned`, `wouldDelete`, `skippedLegacy`,
167
-
`skippedOrphan`, `failed`, `truncated`) across several sweeps.
171
+
3. Set `dry-run`, run a forced relay deploy, and read the sweep counters (`scanned`, `wouldDelete`,
172
+
`skippedLegacy`, `skippedOrphan`, `failed`, `truncated`) across several sweeps. Each sweep records
173
+
them, and the active `mode`, as `relay.managed_endpoint_reaper.*` attributes on its
174
+
`relay.managed_endpoint_reaper.sweep` span in Axiom.
168
175
4. Run the disposable-host canary below.
169
176
5. Set `enabled` only after the canary recovers without a server restart.
170
177
171
178
The job runs every five minutes with a five-minute grace period for tunnels that lost their
172
179
connector, so a candidate is usually removed five to ten minutes after it goes down. Tunnels that
173
180
never connected wait an hour. One sweep attempts at most 100 deletions, so a backlog takes longer.
174
-
`RELAY_TUNNEL_CLEANUP_MODE` is read at deploy time. Changing it, including turning cleanup off during
175
-
an incident, needs a relay deploy.
181
+
Changing `RELAY_TUNNEL_CLEANUP_MODE`, including turning cleanup off during an incident, needs a forced
182
+
relay deploy. Confirm the new `mode` on the next sweep span.
176
183
177
-
To roll back, set cleanup to `off` and deploy the relay before downgrading any host. Keep the
184
+
To roll back, set cleanup to `off` and run a forced relay deploy before downgrading any host. Keep the
178
185
recovery endpoints deployed while current server builds are in use. The nullable columns can stay.
179
186
180
187
### Disposable-host canary
@@ -194,8 +201,8 @@ stage, test Cloudflare account, disposable host, and disposable T3 home. Keep pr
194
201
and pause it with `kill -STOP <first-pid>`. Wait until Cloudflare reports it down for over five
195
202
minutes.
196
203
5. Confirm dry-run counts the first tunnel in `wouldDelete` and the second in `skippedLegacy`.
197
-
6. Set cleanup `enabled` on the disposable stage and deploy. Confirm in the test Cloudflare account
198
-
that the first tunnel is deleted and the legacy tunnel still exists.
204
+
6. Set cleanup `enabled` on the disposable stage and deploy it with `--force`. Confirm in the test
205
+
Cloudflare account that the first tunnel is deleted and the legacy tunnel still exists.
199
206
7. Resume the first child with `kill -CONT <first-pid>`. Confirm the running server detects the
200
207
repeated rejection, requests recovery, and becomes reachable at the same hostname without a
0 commit comments