Ok. Just wanted that confirmed. We already have a workaround for it so I
was mostly just curious to see if it was needed :).
/ Johan
Den torsdag 10 november 2016 kl. 13:03:36 UTC+1 skrev √:
>
> the host needs to be a stable identifier.
>
> What problem are you trying to solve with the rr dns?
Another piece to the puzzle:
docker <-> docker does work routed through the host as long as the
containers run on different hosts.
It's only when doing docker <-> docker routed through host on the same host
that it doesn't work.
Seems like an issue in the artery or aeron protocol.
Den onsdag
Case:
I have two services (A and B) that wish to talk to each other using
akka-remoting over artery.
Each service executes on it's own machine behind a load balancer mapping a
dns name, e.g. $A resolving -> multiple IP addresses.
For A to talk to B, we can for example execute:
// Make request
One additional piece of info that could be useful:
It works if I let the docker containers call each other by container IP
instead of host IP+fowarding.
Den onsdag 9 november 2016 kl. 19:29:44 UTC+1 skrev Akka Team:
>
> Ah, sorry, didn't notice it in the command line.
>
> Can you verify with
With akka.loglevel = DEBUG i only get two more lines on the consumer side:
First
[DEBUG] [11/09/2016 20:29:02.937] [aeron-client-conductor] [akka.remote.
artery.ArteryTransport(akka://consumer-system)] onAvailableImage from
172.17.0.1:52515 session 2110811048
And then a few seconds later
Ok hm sorry.. this is a lot of new things to take in for me :).
How do I change debug level for akka? Is there a typesafe/akka conf
parameter?
I may try the FlightRecorder later if I have time. I think we're probably
going to stick with netty.tcp for now though while artery has some time to
New info.
I have now tested regular udp docker <-> docker - with the exact same
application repurposed for raw java udp sockets. Using the same command
line arguments.
*It works fine with regular udp docker<->docker*. It's just artery that
doesn't want to work for me I suppose :(.
Could it be
New info.
I have now tested regular udp docker <-> docker - with the exact same
application repurposed for raw java udp sockets. Using the same command
line arguments.
*It works fine with regular udp docker<->docker*. It's just artery that
doesn't want to work for me I suppose :(.
Could it be
Well, host <-> docker container artery works (both permutations). It's just
docker <-> docker on the same host that doesn't.
So udp forwarding seems to work. I will try to figure out a non-artery way
of testing udp. Might end up writing a small scala echo server + client
with udp (im terrible
Yes - i Did. Please see my original post for details. You will see that I use
the udp parameter for my docker port forwarding. Also please note that I've
tested artery successfully in docker as long as one of the applications is
running outside docker. However the problem occurs only when both
I'm pretty new to Akka and am currently trying out Akka's new Artery
backend for akka-remoting
(http://doc.akka.io/docs/akka/2.4/scala/remoting-artery.html) while also
testing the regular netty.tcp transport
(http://doc.akka.io/docs/akka/2.4/scala/remoting.html).
It looks fairly straight
11 matches
Mail list logo
