Using akka-2.4.11 on Ubuntu-16.04: If I pull the network plug for a few
seconds while an actor is running I get the errors below.
It looks like akka kills the ActorSystem. How do you prevent this or
recover from it?
(I think it was the same under 2.4.14 when I tested it)
16:16:57.508 ERROR
Assuming that your "products" can be grouped according to what they're
sensitive to, you may find that you can get quite significant performance
benefits by routing all the underlying data that a group of products are
sensitive to and pricing them collectively.
I've had significant success using
Justin,
Once again, thank you so very much for your input.
It is much appreciated.
Now we need to do our homework and build out a strawman
Thanks again,
-- Chris
On Tuesday, December 13, 2016 at 7:38:51 AM UTC-6, Justin du coeur wrote:
>
> On Mon, Dec 12, 2016 at 11:57 PM, Chris Berry
Yes, I've tried. It looks like cluster is handing up.
On Friday, December 9, 2016 at 7:46:27 PM UTC+3, Konrad Malawski wrote:
>
> Have you tried issuing Down to that node via JMX (connecting to a
> different one of course)?
>
> On Dec 9, 2016 17:11, "Valery Dubrava"
>
Opps - see: https://github.com/akka/akka-http/pull/654/files
On Tuesday, December 13, 2016 at 7:08:19 AM UTC-5,
christop...@metaheuristica.com wrote:
>
> Hello All,
>
> I have been happily using AKKA HTTP for some time, but recently tripped
> over an idiosyncrasy with how it manages URL
Wow . . . that answer was HARD to find . . . but found it thanks to Erik
LaBianca . . .
On Tuesday, December 13, 2016 at 7:08:19 AM UTC-5,
christop...@metaheuristica.com wrote:
>
> Hello All,
>
> I have been happily using AKKA HTTP for some time, but recently tripped
> over an idiosyncrasy
On Mon, Dec 12, 2016 at 11:57 PM, Chris Berry wrote:
> Having an Actor per Product, distributed evenly onto the Shards, makes the
> most sense to me as well. It is simple and straightforward.
> Particularly since each Product could cache it's current Rates.
> In this
On Fri, Dec 9, 2016 at 7:31 PM, wrote:
> I thought I needed to use a GraphStageLogic because I need to do the
> following:
>
> request url for page of data and push
> if response has next token, grab another page and push
> continue until no next token
> complete the stream
>
Hello All,
I have been happily using AKKA HTTP for some time, but recently tripped
over an idiosyncrasy with how it manages URL encoding.
I am writing a client to connect to an S3 storage platform (proprietary 3rd
party solution).
That platform requires the Plus (+) Symbol to be URL encoded
Hi Luis,
Sharding allows for a custom ShardAllocationStrategy, which has two
purposes: allocating new shards and taking decisions about rebalancing.
Maybe this could cover what you want to do. (See API here:
10 matches
Mail list logo