Hi,
I'm having problem where `Send` message sent to `ClusterClient` is
delivered to `DeadLetters` inside the cluster. Please see logs on
Stackoverflow question:
http://stackoverflow.com/questions/43775075/message-from-clusterreceptionist-doesnt-reach-distributedpubsubmediator
Somebody please
Hi Manuel,
how did you determine that the problem is related to Akka? What did the
profiling say and where's the bottleneck now?
Answering your questions:
On Friday, April 28, 2017 at 12:10:50 AM UTC+2, Manuel wrote:
I guess that non-blocking code using Futures and work stealing by the
>
Hi Richard,
the behavior you describe is as expected. The ask ActorRef has no relation
to the connection and so watching it doesn't have the desired effect.
The routing DSL doesn't even know about the concept of connections. It only
handles single requests and doesn't get notified in any way
Hi,
Some more newbie questions, so to keep my testing/learning, i want to use
actor to process message. So in my map() i invoke the actor.
1, is this a good use of actor here?
2, Await.result is blocking, in this case is it a good idea to do
non-blocking (or possible)?
Thanks
Shannon
Hi All
Is there any example of using ConstructR with ClusterClient.
I am having AKKA cluster bootstrapped with ConstructR and Zookeeper, i.e. I
have no predefined seed nodes to create ClusterClient.
So, I should connect too Zookeeper and retrieve seed nodes set by
ConstructR.
What is the
Got it working with this, still try to understand the last part (runForEach)
s.mapAsyncUnordered(3, new
Function,NotUsed>>,
CompletionStage>() {
public CompletionStage apply(
Pair