I'm looking for some solid advice on how to handle capturing and storing large memory crash dumps (over 100GB) from a Windows pod in Azure Kubernetes Service (AKS) when it crashes. I want to make sure these dumps are saved correctly, without any corruption, so I can download or inspect them later. I've attempted using a premium Azure disk (az-disk), but it's been unreliable for this situation. I'm also considering options like emptyDir, though I haven't tried that yet. Any suggestions would be really appreciated!
3 Answers
Handling those large dumps in Windows pods can be tricky. It's worth considering that maybe you need to rethink how you're capturing them. If the application is generating massive memory dumps, maybe there’s room for some refactoring there too. Just a thought!
I'm curious to know if you've found a solution yet! Also, your title had me chuckling because I misread it at first—thought it was something totally different!
What exactly is your use case? Are you trying to debug a specific application? Sometimes, context can help figure out how to handle those dumps more effectively.
Yes, I'm trying to debug the application that's running in the Windows pod. To be honest, I'm not a fan of wrestling with Windows containers in Kubernetes!
Haha, I guess I should've been clearer by including 'memory' in the title!