Files mkdir can return Index busy during new Home setup under load #859

Open
opened 2026-10-02 16:40:57 +00:00 by kayg · 0 comments
Owner

The agenda-decks production replay received this response on its disposable local server immediately after passkey setup and two successful folder creations:

POST /api/v1/files/mkdir, body {"path":"Notes/Journal"}

503 {"error":{"code":"service_unavailable","message":"Index is busy; retry shortly"}}

The fixture has a private instance and Home. It runs on the shared build host under heavy load. Head: e585e764c. Server build: agenda-decks, with the four approved merge branches. This interrupted the browser run before Calendar opened. The prior run passed this setup and loaded images, so the response is intermittent.

Check whether Home initialization and the Files Index writer can hold a write transaction long enough to reject a normal folder creation. Keep the server's single-writer invariant. A client can retry this documented busy response once; a persistent failure must remain visible. The UI job keeps all successful-status assertions and records the retry rather than accepting 503 as success. No production server behavior was changed for this finding.

The agenda-decks production replay received this response on its disposable local server immediately after passkey setup and two successful folder creations: `POST /api/v1/files/mkdir`, body `{"path":"Notes/Journal"}` `503 {"error":{"code":"service_unavailable","message":"Index is busy; retry shortly"}}` The fixture has a private instance and Home. It runs on the shared build host under heavy load. Head: e585e764c. Server build: agenda-decks, with the four approved merge branches. This interrupted the browser run before Calendar opened. The prior run passed this setup and loaded images, so the response is intermittent. Check whether Home initialization and the Files Index writer can hold a write transaction long enough to reject a normal folder creation. Keep the server's single-writer invariant. A client can retry this documented busy response once; a persistent failure must remain visible. The UI job keeps all successful-status assertions and records the retry rather than accepting 503 as success. No production server behavior was changed for this finding.
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#859
No description provided.