failureDetectionTimeout - 6
joinTimeout - 12
Saw these recomendations in one of the answers in your forum
On Mon, Jan 14, 2019 at 2:21 PM Stephen Darlington <
stephen.darling...@gridgain.com> wrote:
> Glad you managed to resolve it. What did you have to increase the values
> to?
>
>
Glad you managed to resolve it. What did you have to increase the values to?
Regards,
Stephen
> On 14 Jan 2019, at 09:34, Alena Laas wrote:
>
> It seems that increasing joinTimeout and failureDetectionTimeout solved the
> problem.
>
> On Fri, Jan 11, 2019 at 5:24 PM Alena Laas
It seems that increasing joinTimeout and failureDetectionTimeout solved the
problem.
On Fri, Jan 11, 2019 at 5:24 PM Alena Laas
wrote:
> I attached part of the log with "node failed" events (100.99.129.141 - ip
> of restarted node)
>
> These events are repeated until suddenly after about 40 min
We are using Azure AKS cluster.
We kill pod using Kubernetes dashboard or through kubectl (kubectl delete
pods ), never mind, result is the same.
Maybe you need some more logs from us?
On Thu, Jan 10, 2019 at 7:28 PM Stephen Darlington <
stephen.darling...@gridgain.com> wrote:
> What kind of
What kind of environment are you using? A public cloud? Your own data centre?
And how are you killing the pod?
I fired up a cluster using Minikube and your configuration and it worked as far
as I could see. (I deleted the pod using the dashboard, for what that’s worth.)
Regards,
Stephen
> On
