Re: [akka-user] akka stream kafka newbie question

A Sink is a Graph; as is a Flow, and a Source - they're all graphs, of a specific shape. Here, the method takes a Graph

[akka-user] akka stream kafka newbie question

Hi, I am new to akka stream kafka, and am trying to follow some the examples to get start. I try to use Source.runWith(Sink.ignore()) or Soruce.runWith(Producer.commitableSink(producerSettings) and get this compilation error The method

Re: [akka-user] How to avoid saturation in Akka HTTP (latency spikes)?

Hi, It's me again. After rewriting the full app to make it fully non-blocking (with Slick 3, a non-blocking Redis client, a non-blocking ElasticSearch client, etc.), everything runs much better... but not perfectly. The app still encounters starvation problems. I don't see anything strange in

[akka-user] Re: Best way to handle large response from Actor

Thanks for all your suggestions. We are most likely going to send the notification in message and data will be transferred using MongoDB. We wanted to avoid another query on the receiving end, but looks like that's the best way to go for now. On Thursday, April 27, 2017 at 11:04:57 AM UTC-4,

[akka-user] Re: is it possible to assure every message to be processed

Yes... the default in akka is at-most-once due to the performance hit that is inevitable with guaranteed delivery. To guarantee delivery you must have message persistence, but there are a number of ways to achieve this. We built a financial system with akka and used a few different tools for

Re: [akka-user] Actor name is not unique after termination when running from unit tests

In other words, only the *parent* of the stopped actor can safely "aha! I've seen it stopped, so I'll start a new one with the same name". This is documented behavior in the Actor docs :) -- Konrad `ktoso` Malawski Akka @ Lightbend On 28 April 2017 at

Re: [akka-user] Actor name is not unique after termination when running from unit tests

Hi Piotr, the test thread having observed the termination does not mean that the user guardian (/user) has observed it. On Thu, Apr 27, 2017 at 4:53 PM, Piotr Droździel wrote: > Hello, > Akka docs say: > >> Warning >> >> Keep in mind that an actor stopping and its name

[akka-user] Actor name is not unique after termination when running from unit tests

Hello, Akka docs say: > Warning > > Keep in mind that an actor stopping and its name being deregistered are > separate events which happen asynchronously from each other. Therefore it > may be that you will find the name still in use after gracefulStop() > returned. > In order to guarantee

[akka-user] Re: Querying Snapshot messages using Akka Persistence Query

пятница, 11 марта 2016 г., 10:48:31 UTC+2 пользователь aga...@sointeractive.pl написал: > > Hello! > I was looking for and not found anywhere any information about ability to > get snapshots from snapshot store using Akka Persistence Query. Do you know > any way of doing such a thing? >

[akka-user] Re: Best way to handle large response from Actor

Two possibilities: 1. Go out-of-band and drop down to Http using, say, Netty. Flink does this (it uses Akka remoting for command-and-control but transmits data using Netty). 2. Stick the files on a blob store like S3 and just send messages telling the other actor a file is available (or

Re: [akka-user] is it possible to assure every message to be processed

Hi! On Thu, Apr 27, 2017 at 9:08 AM, Laxmi Narayan wrote: > Hi , > > I am working a high scalable application where I want to use akka as > processing framework. > > But after reading not 100% guaranteed delivery I am actually afraid of > using it. > Nothing in the world

Re: [akka-user] Role of Akka in SMACK

On Thu, Apr 27, 2017 at 10:39 AM, Shiva Ramagopal wrote: > Hi, > > I have read through multiple articles describing the SMACK stack but I'm > having difficulty understanding the role of Akka in the stack. How does > Akka fit in? > Akka is for building the application itself.

Re: [akka-user] Best way to handle large response from Actor

For that kind of "messages" I'd recommend using URLs and using a transport protocol with builtin resumes etc, such as HTTP, FTP etc. On Wed, Apr 26, 2017 at 8:19 PM, Sumanta Dutta wrote: > Hi, we generally use ask pattern to handle request-response between client > and Akka

Re: [akka-user] Best way to handle large response from Actor

I don't know that there's a perfect solution to that problem. Personally, I wound up building a rough but functioning streaming system for this purpose, which sets up protocol Actors at both ends to deal with

Re: [akka-user] Is Akka Multi Node Testing available in Java

Moreover, a very good opportunity for a community contribution : https://github.com/akka/akka/issues/18109 Cheers, Francesco On 27 April 2017 at 03:06, Dai Yinhua wrote: > OK, thanks. > > On Tuesday, 25 April 2017 16:59:10 UTC+8, Akka Team wrote: >> >> Hi Dai, >> >> I'm

[akka-user] Best way to handle large response from Actor

Hi, we generally use ask pattern to handle request-response between client and Akka Cluster. The client waits on the Future. We have a need where the response size (~150MB) is too large to fit in one message even after increasing message-frame-size to - maximum-payload-bytes = 5000

[akka-user] Role of Akka in SMACK

Hi, I have read through multiple articles describing the SMACK stack but I'm having difficulty understanding the role of Akka in the stack. How does Akka fit in? Also I would like to know of experiences in using Akka Streams vs Kafka Connect for ingesting from Kafka into HDFS (Hive) and RDBMS.

[akka-user] is it possible to assure every message to be processed

Hi , I am working a high scalable application where I want to use akka as processing framework. But after reading not 100% guaranteed delivery I am actually afraid of using it. I have checked supervision strategy example but I am afraid of using it inside application. It says I will x