Re: [akka-user] handleWithSyncHandler, handleWith, handleWithAsyncHandler

Thank you On Wednesday, 1 June 2016 13:59:10 UTC+5:30, Konrad Malawski wrote: > > Use Async and complete with Future.successful / Future.failed which don't > go via async ;) > > -- > Konrad `ktoso` Malawski > Akka @ Lightbend > > On 1 June 2016 at

Re: [akka-user] Am I Reinventing the Wheel?

They are updated from a DistributedPubSub topic. Each of them gets the update messages and then recalculates the data they need to maintain locally. So essentially they all function as independent actors, isolated from each other, knowing nothing about each other. This object is one of the

Re: [akka-user] Am I Reinventing the Wheel?

How are you coordinating state between logically-equal actors on different physical nodes? On Wednesday, June 1, 2016 at 3:24:57 PM UTC-6, kraythe wrote: > > So the reason I didn't think this was cluster sharding is that I actually > want these supervisor actors (and their supervised children)

[akka-user] [ANN] Deadline extended! Erlang Workshop 2016

Paper submission deadline extended: 10 June, 2016 Apologies for any duplicates you may receive. CALL FOR PAPERS === Fifteenth ACM SIGPLAN Erlang Workshop -- - Nara, Japan, September 23, 2016 Satellite event

Re: [akka-user] Am I Reinventing the Wheel?

So the reason I didn't think this was cluster sharding is that I actually want these supervisor actors (and their supervised children) to be REPLICATED on every node (they handle user requests). Basically if there is an actor with key 10, I want one actor with key 10 per node. I didn't want

Re: [akka-user] Am I Reinventing the Wheel?

Hmm, on one node? How Ok I will look at docs ... kind of thought I might be reinventing the wheel? Can I send to one router and have the message redirected to the actor with the right key ? On Wednesday, June 1, 2016 at 3:42:16 PM UTC-5, Konrad Malawski wrote: > > > I was working on a

Re: [akka-user] Dependent Processing with Millions of Records without Backlogging?

Yes, that sounds reasonable. Perhaps a kind of natural batching that accumulates changes as long as the previous sort is being executed? Sent from my iPhone > On 01 Jun 2016, at 22:43, kraythe wrote: > > Perhaps, though honestly the entire problem scope is in the post, just

Re: [akka-user] Dependent Processing with Millions of Records without Backlogging?

Perhaps, though honestly the entire problem scope is in the post, just generically expressed. :) I cant be more specific because of NDAs though. Basically the B's job is to maintain a sort order of a specific collection of As and when As mutate resort them. It also and manage other metadata

Re: [akka-user] Am I Reinventing the Wheel?

I was working on a supervisor that lazy creates actors based on some key and then will forward messages to that actor. That's Cluster Sharding :-) http://doc.akka.io/docs/akka/snapshot/scala/cluster-sharding.html Technically you can use it on one node too, yeah. Happy hAkking! -- Konrad

[akka-user] Am I Reinventing the Wheel?

I was working on a supervisor that lazy creates actors based on some key and then will forward messages to that actor. However, it just seems like I am doing something frightfully common. So I was wondering if anyone knows something in Akka that already does this and I should use that. I have

Re: [akka-user] Dependent Processing with Millions of Records without Backlogging?

It seems that your initial description is too vague for direct help—that sorting aspect is not really clear, at least to me. > 1 jun 2016 kl. 20:04 skrev kraythe : > > Pardon? I just said the users are observing the state and observing it change > in real time. > > On

[akka-user] Re: Akka-Http perf difference chunked vs non-chunked

I'd recommend you to use wireshark and look at how the JDK http client you are using actually is sending the data, also, let us know if you can get the same result but using other http clients. curl and wget comes to mind. -- Johan On Wednesday, June 1, 2016 at 11:42:04 AM UTC+2, daleksan

Re: [akka-user] Dependent Processing with Millions of Records without Backlogging?

Pardon? I just said the users are observing the state and observing it change in real time. On Wednesday, June 1, 2016 at 10:31:16 AM UTC-5, √ wrote: > > So If no users are looking why does it need to be already updated? > > -- > Cheers, > √ > On Jun 1, 2016 4:44 PM, "kraythe"

Re: [akka-user] Dependent Processing with Millions of Records without Backlogging?

So If no users are looking why does it need to be already updated? -- Cheers, √ On Jun 1, 2016 4:44 PM, "kraythe" wrote: > Users are observing their state via web pages. And no, it's not viable to > the business to remove this ability, > > -- > >> Read the docs:

Re: [akka-user] Dependent Processing with Millions of Records without Backlogging?

Users are observing their state via web pages. And no, it's not viable to the business to remove this ability, -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >> http://doc.akka.io/docs/akka/current/additional/faq.html >> Search the

[akka-user] Scala - fromPublisher is not a member of object akka.stream.scaladsl.Source

I just started working with akka streams (2.4.6) and slick (3.1.1) in Scala (2.11.7). I'm using Intellij (not sure if that matters but I thought I'd throw it out there). val scanner: DatabasePublisher[Stage] = db.stream(action.transactionally. withStatementParameters(fetchSize = 5000)) val

Re: [akka-user] Akka-websocket and Akka-http, emit to stream and produce one actor per request

Of course it helps, if I understand, Im' trying to something that cannot be done.. But let's say I have the following problem : An app allow customisation via commands sent to a fixed URL via HTTP POST. But I don't have a fixed url or cannot allow any incoming connexion. That's why I would ike

Re: [akka-user] spray cache and akka http

I made a ticket for it, we'd happily someone do the porting / contribution: https://github.com/akka/akka/issues/20679 -- Konrad `ktoso` Malawski Akka @ Lightbend On 1 June 2016 at 09:48:12, Mohnish Kodnani (mohnish.kodn...@gmail.com) wrote: Hi, We have a

Re: [akka-user] Re: Akka-Http perf difference chunked vs non-chunked

I don't see the project attached anywhere - could you put it on github instead? Thanks for prepping a reproducer. -- Konrad `ktoso` Malawski Akka @ Lightbend On 1 June 2016 at 11:05:05, daleksan (david.aleksandrow...@gmail.com) wrote: Hello Johan,

[akka-user] Re: Akka-Http perf difference chunked vs non-chunked

Hello Johan, thanks for your answer. I have a simple project where the issue can be observed. The project does more - it is an experiment to decouple request processing from their acceptance, but it is a small project so running it should be smooth. 1. extract the Gradle project 2. in one

[akka-user] handleWithSyncHandler, handleWith, handleWithAsyncHandler

- low-level-server-side-api.html - - The following are requestHandler methods - - a Flow[HttpRequest, HttpResponse, _] for handleWith, - a function HttpRequest => HttpResponse for handleWithSyncHandler, - a function HttpRequest => Future[HttpResponse] for

Re: [akka-user] handleWithSyncHandler, handleWith, handleWithAsyncHandler

Use Async and complete with Future.successful / Future.failed which don't go via async ;) -- Konrad `ktoso` Malawski Akka @ Lightbend On 1 June 2016 at 10:28:29, RamuR (ramu.rajaseka...@gmail.com) wrote: - low-level-server-side-api.html - - The

Re: [akka-user] Dependent Processing with Millions of Records without Backlogging?

The question is why you need to update them all the time, who's observing their state? On Tue, May 31, 2016 at 8:52 PM, kraythe wrote: > Sorry you mean other ideas? > > I had considered doing the update of the As inside the Bs since the events > that update A are a lot

Re: [akka-user] spray cache and akka http

Quite honestly it's just one simple file you could copy and adapt for Akka HTTP: https://github.com/spray/spray/tree/master/spray-caching/src/main/scala/spray/caching We'd gladly see this as contribution in Akka HTTP actually, just need to find a place for it. Let us know if you'd like to

[akka-user] spray cache and akka http

Hi, We have a project where we need to talk to hadoop/hdfs to download some files from it. This requires that we have protobuf 2.5.0. This is a new cluster for us and before this the older hadoop version was using protobuf 2.4.0 We were using spray 1.3 and akka 2.3 and things were working

[akka-user] [akka-cluster]: The node State is down, Why leader do not remve it.

the log is follow: 2016-05-31 07:40:54,053 | WARN | lt-dispatcher-16 | ClusterCoreDaemon | 167 - com.typesafe.akka.slf4j - 2.3.10 | Cluster Node [akka.tcp://opendaylight-cluster-data@192.168.23.240:2550] - Marking node(s) as UNREACHABLE [Member(address = akka.tcp://

Re: [akka-user] Akka-websocket and Akka-http, emit to stream and produce one actor per request

Hi! :) On May 31, 2016 1:09 PM, "User 48" wrote: > > I there, > > I would like to create a service who acts as a relay between plain Http POST and WebSocket. The idea is to have this service who forward any POST requests body to a Websocket channel and use the Websocket