docs(rustfs): record the two rc.5 defects, and stop calling this an evaluation #553
Loading…
Reference in a new issue
No description provided.
Delete branch "sean/rustfs-rc5-defects"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Two rc.5 defects were measured while 170 GiB moved off MinIO, and both existed only in a session scratchpad. Filing upstream needs an account this cluster does not hold, so this tree is the record. (1) A recursive listing returns SHORT and reports success: 1,543 objects of 21,638 from the zot bucket root, three times out of three, store idle, HTTP 200, IsTruncated=false; per-directory listings are correct. It made mc diff call 20,095 present objects missing and still makes zot's /v2/_catalog report 12 repositories of 124. (2) A client that lists while it writes provokes GOAWAY(too_many_internal_resets) between nodes every 1.5 to 3 minutes, killing every shard write in flight. The rule both imply: copy and prove ONE prefix at a time, never list a whole bucket to decide what exists. The premise was also false in four places -- 'RustFS holds no live data', 'MinIO keeps every bucket' and 'a PARALLEL S3' still appeared in the doc, the cluster registry, the namespace and the StatefulSet. tests/rustfs.sh now fails if the write-up goes missing or any pre-migration claim returns. Five controls confirmed red. Supersedes #550, which targeted main instead of trunk. https://claude.ai/code/session_01KZoQin34jeyt6nDGqvJA76
7d93dbb20502d6b8d04902d6b8d0493700a37d6f