Skip to content

Retry shadow.data copy and keep the PVC if it fails - #406

Merged
radiken merged 2 commits into
masterfrom
alan/shadow-log-copy-retry
Sep 24, 2026
Merged

radiken merged 2 commits into
masterfrom
alan/shadow-log-copy-retry

Conversation

@radiken

@radiken radiken commented Sep 19, 2026 •

Copy link
Copy Markdown
Contributor

When kubectl cp of shadow.data fails, the run retries it every 60 s for up to an hour. If it still fails, cleanup leaves the PVC in place so the data can be copied by hand, instead of deleting it with the run.

Related to #319

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@radiken radiken changed the title Shadow: retry the shadow.data copy and keep the PVC if it fails Retry shadow.data copy and keep the PVC if it fails Sep 19, 2026
@radiken radiken self-assigned this Sep 19, 2026
@radiken radiken added the ift IFT commitments label Sep 19, 2026
@radiken radiken added this to DST Sep 19, 2026
@radiken radiken moved this to In review in DST Sep 19, 2026
@radiken
radiken marked this pull request as ready for review September 19, 2026 00:30

@AlbertoSoutullo AlbertoSoutullo left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

pull_shadow_logs() is synchronous, but it is called directly from the async _run() method. During every retry interval, time.sleep(60) blocks the event loop so a failed copy can stall the entire experiment process for up to an hour.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@radiken
radiken merged commit 64d2a33 into master Sep 24, 2026
2 checks passed
@radiken
radiken deleted the alan/shadow-log-copy-retry branch September 24, 2026 08:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ift IFT commitments

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants