My case is actually to pass some information like Mapped Diagnostic Context.
Some of my legacy java code is using threadlocal to carry on those MDC
information, that's why I need a way to:
intercept tell : collect threadlocal information and do some wrapping
like MDCCtx(mymessage,
So metrics.
I would suggest piggybacking on kamon: http://kamon.io/
Since the guys have many of the things figured out already - it's open
source so it should be possible to either get metrics from their pointcuts
or piggyback in some other way.
On Fri, May 30, 2014 at 11:58 AM, Leon Ma
The thread local stuff is quite scary in an Actor setting by the way and
if possible it would be best to work around it (in a way other than
setCurrentThreadId - I'm guessing that's your current impl?).
Would you be able to construct MDC on your own, bypassing the threadlocals?
On Fri, May 30,
Hi all.
Probably this is a silly question but I couldn't find any clear answer in
the group or docs.
Suppose I have a cluster with 4 nodes with 2 roles (2 node instances per
role). How could I create two shardings, each one sending messages to the
nodes belonging to a particular role? The
I also found this excellent text describing the supervisor hierarchies.
It's about Erlang but the concepts can be applied to Akka
http://learnyousomeerlang.com/building-applications-with-otp#the-onion-layer-theory
On Thursday, 29 May 2014 13:03:03 UTC+1, Jabbar Azam wrote:
Thanks Conrad I
Hi.
My question is based on the Activator template akka distributed workers.
I have started with it and implemented the needed logic based on my needs,
it's working fine.
Now I'm trying to design a solution that based on the node's capabilities,
automatically increase and/or decrease the
Well, I found that if I include the reference to the sender actor into the
message itself - then it seems to be correctly resolved to external form
akka.tcp://HttpCluster@127.0.0.1:53467/system/testActor1#1703301548
So the sender actor gets it's message if it's sent directly to the sender
from
When a rebalance kicks in from using sharding, does the rebalancing process
consider only entries of a particular type or does it consider all entry
types in the cluster?
For example, if I were to shard different entries (different by name that
is) like so:
