Dear hakkers,
We are pleased to announce the availability of the fourth development
milestone of the new Akka Remoting, codenamed Artery. It’s a development
preview and we encourage you to try it out and give us feedback, but it’s
not intended for production usage yet.
The version number is 2.4-ARTERY-M4 with same artifacts as usual.
It is enabled with the following configuration:
akka.remote.artery {
enabled = on
# The hostname or ip clients should connect to.
canonical.hostname = localhost
# use 0 if you want a random available port
canonical.port = 25520
}
Note that the configuration has changed since M3.
The protocol part of the actor system address is akka, so you need to
change previous akka.tcp to akka in for example configuration of cluster
seed-nodes. Note that this has changed from artery to akka since M3.
A summary of what is included in M4 compared to M3
<https://groups.google.com/d/msg/akka-user/JLbLrLh3vIg/twhLMRg7CQAJ>:
-
send heartbeat messages over the control stream, so that failure
detectors are not disturbed by heavy traffic of ordinary messages
-
support for parallel serialization and deserialization
-
bind hostname and port for usage with Docker or NAT environment
-
many bug fixes, most cluster tests are now passing
The full list of changes since the last milestone is available under the
2.4-ARTERY-M3 <https://github.com/akka/akka/milestone/95?closed=1>
milestone on github for your reference.
We are using Aeron <https://github.com/real-logic/Aeron> as the underlying
transport and are implementing the layers on top using Akka Streams. You
find more details in the design document
<https://github.com/akka/akka-meta/issues/16>.
The development branch is artery-dev
<https://github.com/akka/akka/tree/artery-dev>, in case you want to take a
look or contribute. Issues are labeled with t:remoting:artery
<https://github.com/akka/akka/issues?q=is%3Aopen+is%3Aissue+label%3At%3Aremoting%3Aartery>
.
In the next three weeks we will work on additional hardening and testing,
followed by releasing it in a 2.4.x version of Akka as an optional
transport.
We would also like to ask you to take the Akka Community Survey
<http://blog.akka.io/community/2016/09/01/akka-community-survey-2016>. This
is a great opportunity for you to influence what we will work on next.
Pssst... you can also win a t-shirt.
Happy hakking!
--
Patrik Nordwall
Akka Tech Lead
Lightbend <http://www.lightbend.com/> - Reactive apps on the JVM
Twitter: @patriknw
--
>>>>>>>>>> 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+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
