fix(compression-coordinator): Ensure running Spider jobs always have a dispatch_time. - #2462
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
WalkthroughThe compression coordinator now preserves existing ChangesDispatch timestamp persistence
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related issues
Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
LinZhihao-723
left a comment
There was a problem hiding this comment.
One docstring update otherwise lgtm.
Co-authored-by: Lin Zhihao <59785146+LinZhihao-723@users.noreply.github.com>
Description
The compression coordinator can leave a
Runningjob without adispatch_timeif it restarts afterpersist_spider_job_idchanges the job fromPendingtoRunning, but before the batchedmark_jobs_dispatchedupdate at the end of the polling interval.On the next startup, the recovery process picks up
Runningjobs with aspider_idand resumes them viato_completion(), but does not populate the missingdispatch_time.To keep
dispatch_timerepresentative of when the job was actually dispatched,persist_spider_job_idnow also sets it if it has not already been set by the coordinator. This ensures the timestamp is recorded close to the actual dispatch rather than being reconstructed after a restart.Checklist
breaking change.
Validation performed
Summary by CodeRabbit