Running an Akka cluster on k8s and it is using a downing strategy (let’s say Autodowning), so in the case where a node goes unreachable the container which went unreachable exits. The problem is that this node went unreachable because of a network issue/ issue with the platform provided by k8s and as such the entire pod should be restarted and scheduled onto a new healthy k8s node. Because scheduling can take some time we only want to reschedule the container onto a new pod on a new node if there are unreachability is the cause of the failure. Is there any way to propagate failure messages to the parent in k8s like use an exit code to make the decision of when to restart the container and when to delete the pod.
Related topics
Topic | Replies | Views | Activity | |
---|---|---|---|---|
Akka cluster node unreachable when update distribute data in different nodes | 0 | 440 | August 10, 2022 | |
Self-termination for application running in Kubernetes | 1 | 817 | October 17, 2018 | |
Actor watch in Akka cluster | 2 | 830 | April 23, 2018 | |
Down unreachable node by HTTP | 2 | 1166 | March 2, 2020 | |
How to NOT use akka.cluster.auto-down-unreachable-after | 3 | 2883 | October 2, 2018 |