[akka-user] Entity streaming

2016-11-18 Thread Richard Rodseth
Trying this out for the first time. I get a 200 OK but empty body. val eventsRoute = path("events") { get { //val results: List[String] = List("One", "Two", "Three") val results: Source[String, NotUsed] = Source(List("One", "Two", "Three")) complete(results)

Re: [akka-user] Problems with Persistence when rolling nodes.

2016-11-18 Thread kraythe
Indeed I issue a cluster.leave() when the node leaves and I wait for the MemberRemoved before terminating the actor system. Alas I don't have access to the SBR because we are not a commercial customer and can't be until our product starts showing revenue. A snippet of the receive loop is below:

Re: [akka-user] Problems with Persistence when rolling nodes.

2016-11-18 Thread kraythe
Roland, I am wondering how that can happen. When the new node comes in I was under the impression a rebalance would happen with cluster sharding and the actors would be shut down on the old node and started on the new node. Do I have to do something specific other than a cluster.join() to make

Re: [akka-user] Problems with Persistence when rolling nodes.

2016-11-18 Thread Konrad Malawski
Depends if you down them or not. Please read up on downing (split brain resolver docs are also a great read), don't use auto-downing but do use cluster.leave() or .down() to down nodes, then balancing happens. -- Konrad `ktoso` Malawski Akka @ Lightbend

Re: [akka-user] Problems with Persistence when rolling nodes.

2016-11-18 Thread Roland Kuhn
Hi Robert, I cannot comment on whether mysql-async has issues, but assuming that it does not this would point towards having two actors with the quoted persistenceId active at the same time. Regards, Roland > 18 nov. 2016 kl. 17:49 skrev kraythe : > > Greetings, I am

[akka-user] Problems with Persistence when rolling nodes.

2016-11-18 Thread kraythe
Greetings, I am currently using the community plugin for mysql ("com.github.mauricio" %% "mysql-async" % "0.2.16") for AKKA persistence. However, when I perform a rolling restart I get exceptions like the following: Nov 18 10:11:20 vtest-app01 application-9001.log: 2016-11-18 16:11:19 >

Re: [akka-user] Resumable Projection

2016-11-18 Thread Richard Rodseth
Actually, I was referring to this http://doc.akka.io/docs/akka/2.4.12/scala/persistence-query.html#Resumable_projections We are using Kafka upstream from this. A (persistent) actor A consumes the Kafka stream. Another persistent actor B uses eventsByTag(A) and runs a stream with several stages.

Re: [akka-user] Resumable Projection

2016-11-18 Thread Akka Team
Hi Richard, This is not handled by streams itself as it is a feature that Sources must support. I think the most common solution people use for this is Kafka. There is a Streams connector for Kafka: https://github.com/akka/reactive-kafka -Endre On Tue, Nov 15, 2016 at 3:04 AM, Richard Rodseth

Re: [akka-user] Re: Streams and CLOSE_WAIT connections

2016-11-18 Thread Андрей Кузнецов
Hi Reza, At the moment of discussion there was no eagerComplete option. Thanks for mentioning it, i've just got rid of completeSink and everything is working perfectly! On Friday, 18 November 2016 10:33:19 UTC+3, Reza Samee wrote: > > Hi guys; I'm sorry for replying to this old thread but I'm

Re: [akka-user] Using "Distributed Data" for caching Tokens. Delete by value with LMWMap possible?

2016-11-18 Thread Patrik Nordwall
I think you need to store that projection in another key. On Tue, Nov 15, 2016 at 9:31 PM, Qux wrote: > Hello, > > I'm using Distributed Data for caching Authorization-Tokens: > > private final Key dataKey = LWWMapKey.create("cache"); // > token -> CustomerId > > >

Re: [akka-user] Re: Akka cluster sharding messages default serialization

2016-11-18 Thread Patrik Nordwall
That is right, we use Protobuf for all Akka internal messages and persistent events/snapshots. /Patrik On Tue, Nov 15, 2016 at 12:54 PM, Leonard Ehrenfried < leonard.ehrenfr...@gmail.com> wrote: > I'm going to answer my own question here. > > It turns out that akka-cluster-sharding registers

Re: [akka-user] Is it a bug in deployment configuration?

2016-11-18 Thread Patrik Nordwall
The intention is that /system should not use deployment configuration. akka.actor.deployment is supposed to be for /user actors. Unfortunately there is a bug, that nowadays must be treated as a feature, that system actors below the first level, e.g. /system/foo/bar, are actually picking up the