Skip to content
wabe Disk

Evict a disk

Start a self-hosted server and use its connection variables for these requests.

Endpoint

Section titled “Endpoint”
POST /v1/disks/{disk}/evict

Request

Section titled “Request”
Terminal window
curl --fail-with-body -X POST "$WABE_DISK_URL/v1/disks/demo/evict" \
  -H "Authorization: Bearer $WABE_DISK_API_KEY"

Response

Section titled “Response”
200
{"success":true}

The operation drains active disk requests, confirms persistence, closes the writer and removes that disk’s managed RAM/SSD caches. Authoritative stored data remains. Later access reopens the disk, including a request already waiting for eviction to finish.

An unconsumed file/listing/scan response holds a request lease and can delay eviction. Closing or consuming the response releases it. The transition is owned by the server and continues if the eviction caller disconnects. Cleanup proceeds only after persistence succeeds.

The endpoint provides explicit unloading. The standalone server has no automatic idle-eviction timer and no persistent disk-deletion endpoint.

Errors

Section titled “Errors”

400 for an invalid disk name, 401 for authentication, and 500 for storage or cleanup failure. A failed persistence barrier retains the local disk state. See persistence and concurrency.