fix(fleet-queue): align job timeout, lock TTL, and worker sleep - #68
Open
tiweb442 wants to merge 1 commit into
Open
fix(fleet-queue): align job timeout, lock TTL, and worker sleep#68tiweb442 wants to merge 1 commit into
tiweb442 wants to merge 1 commit into
Conversation
Raise ProcessFleetArrival timeout and destination lock TTL to 600s so large battles are not killed mid-lock, allow more lock-contention retries, and poll the queue every 0.5s for snappier delayed arrivals. Co-authored-by: Cursor <cursoragent@cursor.com>
This was referenced Jul 20, 2026
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
1 participant
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.
Summary
Small hardening on top of the fleet arrival queue work in #1413 (addresses remaining responsiveness / large-battle concerns raised on #817):
ProcessFleetArrivaltimeout 120 → 600s and destinationCache::lockTTL 180 → 600s so a long battle cannot be killed while still holding the lock$tries3 → 10 so lock-contentionrelease(30)loops survive longer battles--sleep=0.5 --timeout=600for snappier delayed arrivals and matching worker kill timeoutTest plan
FleetArrivalQueueTeststill passesMade with Cursor