Repository navigation
Alert on feed-recovery relation drift; document repin - #216
Merged
Merged
Conversation
Dataset rollouts added tables to ask_public_core_v1 without updating /etc/zecblock-ask-recovery/config.json, so feed-recovery.py has reported blocked/copy_incomplete since 2026-10-31 13:53 UTC and would not resume a disconnected feed. The availability alert now compares the installed recovery config with pg_subscription_rel (recovery_relations_drift), and feed-recovery.md documents the reviewed repin with its rollback first. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 3 Skipped Deployments
|
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
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.
Problem
Each Zift dataset batch added tables to the
ask_public_core_v1subscription (8 → 15) but not to the host's/etc/zecblock-ask-recovery/config.json. Since 2026-10-31 13:53 UTC (batch 1 rollout),feed-recovery.pylogsblocked / copy_incompleteevery run, so a publisher restart or transport disconnect would not be auto-resumed. Nothing alerted.Change
analytics-availability.py: the read-only probe also lists subscribed relations and compares them with the installed recovery config. A mismatch raisesrecovery_relations_drift(unreadable config:recovery_config_unreadable; no config installed: no check).feed-recovery.md: reviewed repin procedure for adding a replicated table, rollback first. Updating the list changes the pinned digest, so the saved origin floor must be re-armed from a healthy observation, not by deleting state.Not done (needs owner approval)
No host change. Applying the repin (config + state edit, then one oneshot) and deploying this alert are separate approved steps. Once deployed before the repin, the alert will fire
recovery_relations_driftuntil the repin lands.🤖 Generated with Claude Code