Uploads stall during user purge #193

Closed
opened 2026-09-26 15:34:19 +00:00 by kayg · 2 comments
Owner

Finding from the local real-server adversarial run on 2026-09-26.

During the user-purge check in tests/adversarial/attack2.py, a write completed but took 8.38 seconds; the probe expected it to complete in under 2 seconds and reported write during user purge: upload took 8.38s; expected under 2 s.

The shared host load average was around 49–51, with multiple Calternal servers and adversarial jobs active. The probe did not label this SLOW, so reproduce the write during purge on a quiet host and verify the purge flow does not hold unrelated writes for several seconds.

Finding from the local real-server adversarial run on 2026-09-26. During the user-purge check in `tests/adversarial/attack2.py`, a write completed but took 8.38 seconds; the probe expected it to complete in under 2 seconds and reported `write during user purge: upload took 8.38s; expected under 2 s`. The shared host load average was around 49–51, with multiple Calternal servers and adversarial jobs active. The probe did not label this SLOW, so reproduce the write during purge on a quiet host and verify the purge flow does not hold unrelated writes for several seconds.
Author
Owner

Duplicate and already-fixed evidence: #78 identifies the instance-wide deletion lock, and #330 tracks the cross-User upload latency with the same under-2-second acceptance check. The merged origin/dev commits f8e93b7e7 and 211dd4577 move heavy deletion work to a restart-safe background Worker and retain the probe. Recommend link this 8.38 s run to #330 as historical evidence; do not close it in this audit.

Duplicate and already-fixed evidence: #78 identifies the instance-wide deletion lock, and #330 tracks the cross-User upload latency with the same under-2-second acceptance check. The merged origin/dev commits f8e93b7e7 and 211dd4577 move heavy deletion work to a restart-safe background Worker and retain the probe. Recommend link this 8.38 s run to #330 as historical evidence; do not close it in this audit.
Author
Owner

Duplicate of the User Home purge contention tracked by #330. The #330 fix is on origin/dev; #330 remains open for its unverified quiet-host latency target.

Duplicate of the User Home purge contention tracked by #330. The #330 fix is on origin/dev; #330 remains open for its unverified quiet-host latency target.
kayg closed this issue 2026-10-03 11:55:43 +00:00
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
kayg/calternal#193
No description provided.