Re: Detecting disk/volume failures in Ozone

Why is the write checksums validation not turned on by default? I have seen cases on HDFS where the "verify checksums on write" feature caught data corruption problems caused by faulty hardware / network cables before it was able to propagate into the system. The only reason I can think of for not

Re: Detecting disk/volume failures in Ozone

I totally agree. We need write checksums on by default, and I am not sure the historical reason they were turned off when they were added in HDDS-5623 . We should at least test to quantify the performance difference of on vs off before we flip the sw