Short answer: a single out-of-space event became permanent because the database could not write to its own log file, reported that failure to stderr for every suppressed message, and Docker's default json-file driver captured stderr into a file whose max-size defaults to unlimited . Freeing the disk brings inserts back and leaves the loop running at full speed, because the logger does not recover without a restart. Judge the repair by the growth rate of whatever ate the disk, not by the absence of errors.
The complaint arrived from the wrong place. A development stand reported that its buffering insert proxy had stopped shipping and was spooling files locally, with its own disk filling up. The cluster it ships to was the thing that was actually down, on both replicas, with zero bytes free.…