You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Like on Windows it should be possible to dump a process without interruption. Procdump -r uses process snapshots.
Actual behavior
During dump generation process is not responding.
The Google dumping tool claims that it is possible:
https://github.com/anatol/google-coredumper
As far as I have read the code it forks the process from the inside to get a copy of everything by calling sys_fork(). Is this something which could be achieved from the outside with procdump as well on Linux, or would one need to bake this capability into the service?
The text was updated successfully, but these errors were encountered:
Thanks for the suggestion. Today, we leverage gcore to do the actual dump generation, but it if we decide to go down the path of using our own core dumper we will definitely take a look at this.
Is this not needed by you internally, or are all your services running in Kubernetes multi instance capable and you simply take a Pod offline and dump it while another one is servicing requests?
Expected behavior
Like on Windows it should be possible to dump a process without interruption.
Procdump -r
uses process snapshots.Actual behavior
During dump generation process is not responding.
The Google dumping tool claims that it is possible:
As far as I have read the code it forks the process from the inside to get a copy of everything by calling sys_fork(). Is this something which could be achieved from the outside with procdump as well on Linux, or would one need to bake this capability into the service?
The text was updated successfully, but these errors were encountered: