I'm looking for some guidance on handling a specific issue with Kubernetes. After a crash, I need to reliably capture and store very large memory crash dumps (over 100GB) from a Windows pod in Azure Kubernetes Service (AKS). It's crucial that these dumps are saved without corruption so I can download or inspect them later.
A bit of context: I've tried using a premium Azure disk (az-disk), but it hasn't been reliable for this. I'm also considering options like emptyDir but haven't tested that yet. Any suggestions would be greatly appreciated. Thanks!
3 Answers
If you find a solid solution, I'd love to hear about it! Your topic made me giggle a bit; initially, I thought you were referring to something else—sometimes you just can't help but let your mind go there, right? But seriously, good luck with your search!
What’s your main goal here? Are you trying to debug the application? I ask because I find dealing with Windows containers in Kubernetes quite challenging. If all you're doing is generating huge memory dumps, maybe there’s a better way to manage your app to minimize that?
For handling large memory dumps in Windows pods, you'll definitely need a different approach. Instead of focusing solely on saving dumps, consider looking into application refactoring. It might not be what you want to hear, but flushing unnecessary data and optimizing your app could help you avoid hefty dumps entirely.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures