trade-next/trade-docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(migration): record ingestor canary rollout

Browse Source
This commit is contained in:
mpabi
2026-04-12 17:36:22 +02:00
parent e2c0a04293
commit a1921b213d
1 changed files with 9 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
doc/migration-todo.md
View File

@@ -76,6 +76,9 @@ Date: `2026-04-12`
- Namespace `trade-r001-canary` is live on `sol` with initial quota and limit guardrails, and can reach the shared `Postgres` and `Redis` services in `trade-infra`. - Namespace `trade-r001-canary` is live on `sol` with initial quota and limit guardrails, and can reach the shared `Postgres` and `Redis` services in `trade-infra`.
- The first application surface for `R001` is now live in `trade-r001-canary`: `Hasura`, `trade-api`, and `trade-frontend`. - The first application surface for `R001` is now live in `trade-r001-canary`: `Hasura`, `trade-api`, and `trade-frontend`.
- The target host `Postgres` on `sol` now has `TimescaleDB` installed and a matching application database/user provisioned for `R001`. - The target host `Postgres` on `sol` now has `TimescaleDB` installed and a matching application database/user provisioned for `R001`.
- `trade-ingestor` is now live in `trade-r001-canary` on `sol` in a schema-compatible canary mode that reads from `dlob_stats_latest`.
- Current live `trade-staging` drift was confirmed for `trade-ingestor`: the live script now reads `dlob_hot_derived_latest` and `dlob_all_derived_latest`, but that derived writer chain has not yet been reconstructed in the `sol` canary schema.
- `agave` RPC on `sol` is currently healthy; repeated samples after the canary rollout show slot lag of about `2` versus `api.mainnet-beta.solana.com`.
## Migration Risks ## Migration Risks
@@ -345,7 +348,12 @@ Date: `2026-04-12`
### 22. Migrate publishers and ingest only after storage and Redis validation pass ### 22. Migrate publishers and ingest only after storage and Redis validation pass
- Pending. - In progress.
- Substep A is now in place on `sol`: deploy `trade-ingestor` first in a schema-compatible canary mode and verify its secret wiring, rollout behavior, and Hasura connectivity.
- Substep B remains pending: reconstruct the live `R001` DLOB derived writer chain and the `dlob_*_derived_latest` tables so the canary ingestor can switch from `dlob_stats_latest` to the exact current live query path.
- Done on `2026-04-12`: extended `trade-next/trade-gitops` canary environment with `trade-ingestor`, synced `trade-ingestor-tokens`, and added `trade-ingestor` rollout checks to the `deploy-trade-r001-canary` workflow.
- Done on `2026-04-12`: manually validated `trade-ingestor` on `sol`; deployment reached `Available`, restart count stayed at `0`, and startup logs confirmed `HASURA_GRAPHQL_URL=http://hasura:8080/v1/graphql`, markets `SOL-PERP,PUMP-PERP`, and mode `dlob_stats_ticks`.
- Done on `2026-04-12`: after push of commit `b8f1303`, the GitOps path on `sol` rolled a fresh `trade-ingestor` pod and it remained healthy with restart count `0`.
### 23. Validate host health, agave health, trade health, and end-to-end flow after rollout ### 23. Validate host health, agave health, trade health, and end-to-end flow after rollout