fix(bounds-seeder): target clickhouse namespace + cbt-redis after raw migration#140
Merged
Merged
Conversation
… migration The external-bounds seeder pulled production bounds from `<network>-xatu-cbt-redis-node-0` (secret `<network>-xatu-cbt-redis`) in the `xatu` namespace. Since the clickhouse-raw migration, prod cbt and its Redis moved to the `clickhouse` namespace and dropped the `xatu-` prefix (`<network>-cbt-redis-node-0`, secret `<network>-cbt-redis`). The stale coordinates made `SeedFromProduction` fail silently (non-fatal), leaving local Redis empty so CBT fell back to multi-billion-row min/max scans of external tables on cold start. Verified: lab up now seeds 58 cbt:external:* bound keys into local Redis from mainnet-cbt-redis-node-0 (e.g. canonical_execution_logs min 52029 / max 25371147).
Member
Author
|
thanks @mattevans 👑 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The external-bounds seeder pulled production bounds from
<network>-xatu-cbt-redis-node-0(secret<network>-xatu-cbt-redis) in thexatunamespace, but since the clickhouse-raw migration prod cbt and its Redis moved to theclickhousenamespace and dropped thexatu-prefix (<network>-cbt-redis-node-0, secret<network>-cbt-redis); the stale coordinates madeSeedFromProductionfail silently (it's non-fatal), leaving local Redis empty so CBT fell back to multi-billion-row min/max scans of external tables on cold start. This points the seeder at the current location. Verified locally:lab upnow seeds 58cbt:external:*bound keys frommainnet-cbt-redis-node-0(e.g.canonical_execution_logsmin 52029 / max 25371147), so CBT reads bounds from Redis instead of scanning.