Apologies if this winds up being a duplicate. I searched for a while before posting.
I have trouble debugging HDF5 applications using dataset chunking because the places where things are failing are typically in the H5Dwrite call(s) but I don’t get any error stack or reporting from HDF5 until H5Dclose. At that point, I get a slew of errors at it tries to preempt each chunk from memory to the file. I can’t tell where one chunk errors begin and another’s end.
So, I am wondering if there is a way to sort of force H5Dwrite to “do all its stuff” in the write call itself rather than piling everything up in the cache and doing its work in H5Dclose or H5Fclose. That way, I can more easily localize which writes are failing.
If setting chunk cache size to zero will have the intended effect, that is fine as a debugging aid…though I would hate to accidentally leave such debugging code in any real application.