I'm looking for advice on how to effectively capture and store very large full memory crash dumps (over 100GB) from a Windows pod in Azure Kubernetes Service (AKS) after a crash. My goal is to ensure that these dumps are saved without corruption, allowing for inspection or download later. I've already tried using a premium Azure disk (az-disk), but it hasn't been reliable for this purpose. I'm also considering options like emptyDir, although I haven't tested it yet. Any suggestions would be greatly appreciated!
3 Answers
When dealing with Windows pods, you might need a different approach for large dump files. It might be worth refactoring your application to handle memory dumps more efficiently, rather than relying solely on Kubernetes solutions.
What’s the actual use case for capturing these large dumps? If you're debugging an application, it might help to share more about what you're working on with that Windows pod. Windows containers can be tricky in Kubernetes, and I totally get the frustration!
I'm curious to know if you've found a solution for this! By the way, your title does get a chuckle – at first, I thought we were talking about something else! But seriously, this sounds like a tough spot. Good luck!
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