Closed wallrj closed 6 years ago
Although this doesn't always happen.
Could this perhaps be down to Cassandra not having exited properly or something? Pilot now calls Wait() on the process and will exit when Wait returns. It’d be great if we can isolate what conditions cause this. On Wed, 24 Jan 2018 at 11:24, Richard Wall notifications@github.com wrote:
Although this doesn't always happen.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jetstack/navigator/issues/217#issuecomment-360101258, or mute the thread https://github.com/notifications/unsubscribe-auth/AAMbP_Duw9_aQS_RzIAV5BpuUakjwYQWks5tNxLVgaJpZM4RrGGY .
Looking again at the process tree in the comment above, it occurs to me that the problem was probably that the parent su
command wasn't waiting for and exiting when the cassandra process died.
That should be fixed now that #222 is resolved.
I killed the Cassandra process using kill inside a Cassandra pod in my test cluster.
I expected the Pilot to exit immediately.
What I got was a zombie Java process. And the Pilot kept running until Kubernetes killed it after X failed liveness probes.
/kind bug