Thanks for clarifying that. We suspected that but weren't sure. We can close
this thread ;). Thanks everyone for great input
Skickat från min iPhone
> 10 nov. 2016 kl. 18:03 skrev Patrik Nordwall :
>
> And for the record, it's just accidental that it works with tcp.
Consider that confirmed then. ;)
On Thu, Nov 10, 2016 at 5:12 PM,
wrote:
> 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.
And for the record, it's just accidental that it works with tcp. We don't
guarantee that the same connection is reused.
tors 10 nov. 2016 kl. 17:14 skrev Endre Varga :
> Actor remote messaging is a P2P protocol and as such any kind of
> name-remapping is harmful. Trying
Actor remote messaging is a P2P protocol and as such any kind of
name-remapping is harmful. Trying to load balance Akka Remote connections I
think is a mistake and makes not much sense. You *can* load balance Akka
provided services of course, but you need to expose them as a different
protocol
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?
the host needs to be a stable identifier.
What problem are you trying to solve with the rr dns?
On Thu, Nov 10, 2016 at 10:48 AM,
wrote:
> Case:
>
> I have two services (A and B) that wish to talk to each other using
> akka-remoting over artery.
> Each