Repository navigation
[AURON #2577] Prevent stale Celeborn PID files from blocking CI startup - #2578
Merged
Merged
Conversation
cxzl25
approved these changes
Oct 14, 2026
Contributor
Contributor
Author
|
@cxzl25 @slfan1989 thanks for the reviews |
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.
Which issue does this PR close?
Closes #2577
Rationale for this change
Celeborn CI can intermittently fail after restoring stale PID files from the binary cache. If a cached PID matches an existing Java process, Celeborn incorrectly reports that its service is already running. This was observed in the Celeborn CI check for PR #2575.
What changes are included in this PR?
Create a fresh directory under
RUNNER_TEMPand exportCELEBORN_PID_DIRbefore starting the master and worker. This bypasses cached PID files and keeps new PID files outside the cached installation.Are there any user-facing changes?
No. This change only affects Celeborn startup in CI.
How was this patch tested?
To be verified by the Celeborn GitHub Actions checks.
Was this patch authored or co-authored using generative AI tooling?
If yes, include:
Generated-by: OpenAI Codex (gpt-6)ASF guidance: https://www.apache.org/legal/generative-tooling.html