[akka-cluster] expected-response-after and acceptable-heartbeat-pause

[Jeff]

Can somebody enlighten me on how these two settings interact? These two settings seem to overlap.

Thanks

Jeff

[Patrik Nordwall]

expected-response-after is used for starting failure detection when the first heartbeat message is not received as expected, e.g. when connection is broken from the beginning.

acceptable-heartbeat-pause is explained here: http://doc.akka.io/docs/akka/2.3.11/scala/cluster-usage.html#Failure_Detector

/Patrik

--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+...@googlegroups.com.
To post to this group, send email to akka...@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

--

Patrik Nordwall
Typesafe -  Reactive apps on the JVM
Twitter: @patriknw

[Jeff]

So if my understanding is correct, expected-response-after and acceptable-heartbeat-pause do the exact same thing, the only difference is when they kick in. expected-response-after is for the first heartbeat, and accetable-heartbeat-pause is for every subsequent heartbeat. Is my understanding correct?

Thanks

Jeff

[Patrik Nordwall]

On Tue, Jun 16, 2015 at 8:51 PM, Jeff <jknigh...@gmail.com> wrote:

So if my understanding is correct, expected-response-after and acceptable-heartbeat-pause do the exact same thing, the only difference is when they kick in. expected-response-after is for the first heartbeat, and accetable-heartbeat-pause is for every subsequent heartbeat. Is my understanding correct?

expected-response-after is added on top of the acceptable-heartbeat-pause for the first heartbeat. Now when we discuss it I can't really find a good motivation for that delay, at least not as long as the default 5 seconds. Perhaps it is a leftover from when we used one-way heartbeating, instead of current request-response hearbeating.

Would you mind creating a github issue and we will investigate if that delay can be removed, or reduced.

 

Thanks,

Patrik

[Jeff]

Sure, ticket is here https://github.com/akka/akka/issues/17750