I can’t find anything about cratedb and this error, just elasticsearch. And yes, one of the nodes did get to 96% full disk. But it is now resolved (currently at 75% full) and crate restarted. Not sure how to proceed.
When a disk on a node exceeds the cluster.routing.allocation.disk.watermark.flood_stage threshold, this block is applied (set to true ) to all tables on that affected node. Once you’ve freed disk space again and the threshold is undershot, you need to set the blocks.read_only_allow_delete table setting to false .