Coming into this *not* as a member of the Akka Team, but as a heavy
customer -- this is out of line. I won't claim it's perfect, but both Akka
the system and the supporting documentation are good in the grand scheme of
things, and always getting better.
This sort of rudeness is inappropriate
Bump.
Has anyone implemented a CircuitBreaker-like stage
(mapAsyncWithCircuitBreaker perhaps?) that would provide backpressure?
On Mon, Feb 27, 2017 at 2:18 PM, Richard Rodseth wrote:
> What's the current thinking on this? This ticket is open:
>
>
Hi JM,
You are throwing out some insulting comments that I will not accept. Can
you instead explain what you are having trouble with in a constructive way
and I'm sure someone will try to help or understand the need for
improvements.
Regards,
Patrik
tis 28 feb. 2017 kl. 10:18 skrev Jun Ma
Please provide your inputs to overcome this problem.
Any help is greatly appreciated!
Thanks,
Chaitanya
On Monday, February 27, 2017 at 4:57:34 PM UTC+5:30, Chaitanya Mahipath
wrote:
>
> Hi Johannes,
>
> I tried with Http.SingleRequest as suggested but could see the following
> exception
>
>
Hi Akka team,
I am developing an application with cluster sharding.
And I have below deployment:
server1(3 jvms): seed 1, seed 2, endpoint
server2(2 jvms): worker 1, worker 2
server3(2 jvms): worker 1, worker 2
The seed instance will act only the role of seed, no shard region is
started.
The
What the hack does this mean " it will use what you specified as a
parameter"? Which parameter? You meant the parameter assigned by the "-D"?
Are you Akka guys really programmers? Your doc and product line control
sucks!
What do you guys expect users to keep up with various migrations of Akka?!