Skip to content

dbi 604 handle replication slot creation getting stuck#4439

Open
masterashu wants to merge 3 commits into
mainfrom
dbi-604-handle-replication-slot-creation-getting-stuck
Open

dbi 604 handle replication slot creation getting stuck#4439
masterashu wants to merge 3 commits into
mainfrom
dbi-604-handle-replication-slot-creation-getting-stuck

Conversation

@masterashu

Copy link
Copy Markdown
Contributor
  • Handle status terminating during resync-drop-flow.
  • Add user facing logs for waiting replication slot creation warning.
    • Streaming replication protocol doesn't support timeouts, so best we can do is user warning

@masterashu masterashu requested a review from a team as a code owner June 17, 2026 16:54
@claude

claude Bot commented Jun 17, 2026

Copy link
Copy Markdown

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

1 similar comment
@claude

claude Bot commented Jun 17, 2026

Copy link
Copy Markdown

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

@github-actions

Copy link
Copy Markdown
Contributor

🔄 Flaky Test Detected

Analysis: The actual e2e tests passed; failures are isolated to the "Ingest tests results for analysis" CI infrastructure step, where the analytics ClickHouse endpoint returned HTTP 500 "Timeout error" — a network/infra issue, not a code bug.
Confidence: 0.97

✅ Automatically retrying the workflow

View workflow run

@masterashu masterashu self-assigned this Jun 17, 2026
@github-actions

Copy link
Copy Markdown
Contributor

🔄 Flaky Test Detected

Analysis: The actual test step passed; only the "Ingest tests results for analysis" telemetry step failed because the stresshouse ClickHouse metrics instance rejected the upload with a "Too many simultaneous queries (1007/1000)" rate-limit error after exhausting retries — an infrastructure issue, not a code bug.
Confidence: 0.97

✅ Automatically retrying the workflow

View workflow run

@github-actions

Copy link
Copy Markdown
Contributor

🔄 Flaky Test Detected

Analysis: The actual tests passed; the only failure is the CI "Ingest tests results for analysis" step hitting repeated HTTP 500 "Timeout error" responses from the external analytics-upload endpoint, an infrastructure/network issue unrelated to the test code.
Confidence: 0.97

✅ Automatically retrying the workflow

View workflow run

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant