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
{{ message }}
This repository has been archived by the owner on Nov 12, 2024. It is now read-only.
It looks like akka-raft is configured by default to use TCP between nodes.
I would bet that the implementation could get notably better performance if it used UDP, by avoiding all of the extra network delays implied by TCP. The raft protocol should be resilient to message reorderings, duplicates, drops, etc.
The text was updated successfully, but these errors were encountered:
Good point. @ktoso Are you considering contributions for features like that? As far as I know akka remoting supports plugable transport implementation or its more complicated than that?
It looks like akka remoting supports transport via udp. Netty transport has an udp mode. I've just tried to change the activator template akka-sample-remote-scala to use udp
I wouldn't say this is a direction I'd like to pursue currently, first I'd like to nail correctness.
Since this will be most likely used in Akka Clusters, TCP makes much sense in there, therefore switching to UDP does not seem very realistic for those kinds of deployments (at least with the current remoting impl).
It's a neat idea, but I'd rather stash it for now.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It looks like akka-raft is configured by default to use TCP between nodes.
I would bet that the implementation could get notably better performance if it used UDP, by avoiding all of the extra network delays implied by TCP. The raft protocol should be resilient to message reorderings, duplicates, drops, etc.
The text was updated successfully, but these errors were encountered: