I'm seeking some advice on how to efficiently capture and store very large full memory crash dumps (over 100GB) from a Windows pod in Azure Kubernetes Service (AKS) after it crashes. It's vital for these dumps to be saved without any corruption so that I can download or inspect them later. To give you a bit more context, I've tried using a premium Azure disk (az-disk), but it hasn't been reliable for this particular scenario. I'm also considering options like emptyDir, though I haven't tested those yet. Any thoughts or suggestions would be greatly appreciated! Thanks!
2 Answers
You might want to look into specific storage solutions tailored for large dumps. Azure Blob Storage could be a good option since it handles large amounts of data well. You can set up your application to push dumps directly to it upon crash rather than relying solely on local storage.
Sounds like you need a different strategy for handling those dumps, especially with Windows containers. You could also consider adjusting your application design to minimize the chances of generating such massive dumps in the first place. It's not ideal, but worth exploring if the dumps are consistently that large.
Good point! I’ll definitely keep that in mind. Sometimes I feel stuck with these Windows pods.