I don't think so, but you could use the Cluster Client to easily talk from
one cluster (or some Akka system) to the other.
Heiko
On Fri, May 2, 2014 at 6:05 AM, tigerfoot wrote:
> Can a node be configured to belong to multiple (2) Akka clusters at the
> same time?
>
> I want to have one cluste
Can a node be configured to belong to multiple (2) Akka clusters at the
same time?
I want to have one cluster of private back-channel communication and a
second (possibly with different/overlapping membership) for
public/application-level communication.
--
>> Read the docs: http:
Santoash,
It is certainly possible, but it is confusing. I think what is probably
happening is that you are passing an ActorRef in a message to the
ClusterSingleton. When you create the actor in your local system (even if
it is configured for remoting), you can't then send that actorref in a
Hi,
Apologies for resurrecting a long-dead thread, but I am facing a similar
problem when using remoting with Akka 2.3.0 with Scala 2.10.2.
I have two actor systems:
- remote-registration-service: Runs on localhost:8245, and "registers"
clients
- registration-client-system-{UUID}: Ru
You might find these references helpful:
- Aggregator: https://vaughnvernon.co/?p=539
- Scatter-Gather: https://vaughnvernon.co/?p=561
On Thursday, May 1, 2014 6:51:03 AM UTC-6, Richard Cole wrote:
>
> That's a really interesting proposal, would you recommend that the master
> still handles th
That's a really interesting proposal, would you recommend that the master
still handles the child actors but just passes them a reference to their
newly created aggregated actor at construction?
On Wednesday, 23 April 2014 16:44:24 UTC+1, Richard Cole wrote:
>
> I'm currently using akka to imple
Thank you all for the insightful comments. It turns out that the
unprocessed event was being offered to the processor for replay following
node failure, but our logic verifying event sequence numbers (kicks) was
rejecting it due to environmental setup of the test itself. We are
revisiting our
That's ok. I think I'll try the batching pattern (with max size and max
latency constraints) described in
https://groups.google.com/forum/#!topic/akka-user/todrna9GRS8/discussion
It seems to improve throughput substantially - in a quick test over a
simulated high latency link.
--
>>
