Will the pool shut itself down even if "min-connections" is set greater
than zero?
On Sunday, February 26, 2017 at 9:17:23 AM UTC-8, Johannes Rudolph wrote:
>
> Hi Johnson,
>
> if you use a `cachedHostConnectionPool`, the pool itself is a shared
> resource that is managed by the infrastructure.
Hi
I have a case where I want to use an akka stream with backpressure and
insert messages to the stream from multiple threads.
Here is the code to explain better
import akka.actor.ActorSystemimport akka.stream.scaladsl._import
akka.stream.{ActorMaterializer, OverflowStrategy,
What's the current thinking on this? This ticket is open:
https://github.com/akka/akka/issues/15307
I have an infinite stream communicating with an external service. If the
external service goes down or some threshhold of errors is reached, it may
be appropriate to stop the actor that runs the
Well, scaling down is straightforward: in that case, you *are* taking down
the node (or at least, the ActorSystem), so you should down it. As soon as
you down it, the shards should migrate properly to other nodes. That's
normal stuff. Keep in mind that "unreachable but not down" should be a
On Monday, February 27, 2017 at 10:11:59 AM UTC-8, Justin du coeur wrote:
>
> There's no silver-bullet option for "fault tolerance" in situations like
> this. You absolutely do *not* want to start up alternate versions of the
> sharded entities in this situation -- that's classic split-brain,
There's no silver-bullet option for "fault tolerance" in situations like
this. You absolutely do *not* want to start up alternate versions of the
sharded entities in this situation -- that's classic split-brain, and is
the surest route to data corruption. You could create some sort of
Hello everybody!
I do some research about akka sharding. One moment is not clear for me
right now.
If some node becomes unreachable (crashed but not down, for example) all
shards which belong to this node become unreachable. Which means all
messages to these actors are dropped.
Is it correct?
Yes. Status code, headers & the content using entity.toStrict.
Thanks
On Monday, February 27, 2017 at 5:06:53 PM UTC+5:30, √ wrote:
>
> Are you consuming your response bodies?
>
> --
> Cheers,
> √
>
> On Feb 27, 2017 12:27 PM, "Chaitanya Mahipath" > wrote:
>
>> Hi
Are you consuming your response bodies?
--
Cheers,
√
On Feb 27, 2017 12:27 PM, "Chaitanya Mahipath"
wrote:
> Hi Johannes,
>
> I tried with Http.SingleRequest as suggested but could see the following
> exception
>
> akka.stream.BufferOverflowException: Exceeded
Hi Johannes,
I tried with Http.SingleRequest as suggested but could see the following
exception
akka.stream.BufferOverflowException: Exceeded configured max-open-requests
value of [32]
This time the test has lasted only for 40 odd minutes(as compared to
previous test result which lasted for
Hi Dimitry,
that message is a different one. It means that your code is issuing
requests with an explicit header `RawHeader("User-Agent", ...)` somewhere.
Johannes
On Thursday, February 23, 2017 at 8:10:03 PM UTC+1,
dmitriy...@alisagaming.com wrote:
>
> Hi everyone.
>
> I've been using akka
Hello,
the error is thrown
here:
https://github.com/akka/akka/blob/master/akka-stream/src/main/scala/akka/stream/impl/io/TcpStages.scala#L303.
I agree it's hard to see why that error would happen. One thing that could
have happened is that a connection attempt was very slow and so the
12 matches
Mail list logo