[akka-user] ActorPublisher GraphStage alternative?

Hi, I see in the docs for 2.5.2 that ActorPublisher/ActorSubscriber will be deprecated. In my (still beginning) experiments with akka streams I used ActorPublisher as a way to help create some back pressure controls while consuming messages from an external queue. This worked just by

Re: [akka-user] Akka stream - Source of http response.

Hi Alejandro, I don't get the question - could you rephrase it a bit (more details)? An HttpRequest simply contains a Source[ByteString, _] and that "just works"™. -- Konrad `ktoso` Malawski Akka @ Lightbend On 26 May 2017 at 00:21:38, Alejandro Merchan

Re: [akka-user] Dispatcher configuration ?

The most important is that you put the blocking actors/task on a dedicated dispatcher, and don't run them on the default dispatcher. http://doc.akka.io/docs/akka/current/scala/general/actor-systems.html#blocking-needs-careful-management /Patrik On Thu, May 25, 2017 at 5:52 PM, Vishnu Vardhan

Re: [akka-user] Re: Issue in Sending messages through akka cluster.

Work pulling (see my previous link) might be a good choice. Note that it's not only about that the end consumers might not consume fast enough, it's also anything on the way there, such as serialization and deserialization (which I think is your bottleneck). On Thu, May 25, 2017 at 1:16 PM,

Re: [akka-user] ANNOUNCE: New Akka documentation, website and Akka 2.5.2 released

On Thursday, May 25, 2017 at 4:23:02 AM UTC-4, Konrad Malawski wrote: > > Hi Lee, > RSS works for me, do you use this feed: http://akka.io/rss.xml ? > > Konrad, Thank you for checking. For the sake of discussion & common reference, I use the Lightbend site as reference. Yes, I understand that

Re: [akka-user] cluster sharding and auto-down

Clarifying question: are you doing downing somewhere in this? The naive auto-down feature shouldn't be used because it is *too* naive, and leads to split-brain when you get transient network failures. But you do still have to down nodes *somehow* when they crash, so that the system knows to

[akka-user] cluster sharding and auto-down

I am using *akka cluster sharding *to build a long running calculation service, and I have set auto-down to false. And we have mechanism that *when one jvm get crashed it will be restarted immediately* by some external monitoring tools. I would like to confirm below behaviors when some jvm get