[akka-user] Routing Kafka messages to websocket

This question was not answered at https://stackoverflow.com/questions/36348020/kafka-message-to-websocket so I ask here. Thanks Vish === I am trying to write a Kafka consumer to websocket flow using reactive-kafka, akka-http and akka-stream. val publisherActor = actorSystem.actor

Re: [akka-user] [reactive-kafka 0.9.0.1] Why is my use of reactive-kafka so slow on commit?

Ok, I've made some progress but I'm seeing crashes now. I can easily populate a set number of messages into a topic. No issues, and offsets are properly set. My consume code with 0.11-M1: count = 0 val consumerSettings = ConsumerSettings(as, new ByteArrayDeserializer, new StringDeseri

Re: [akka-user] Re: issue with receiveRecover and router

If you start two persistent actors they will recover independently of each other. That doesn't change because they are in a router pool. Probably you also used the same persistenceId for both instances and that is not allowed. Sounds good that you use a different design. /Patrik fre 1 apr. 2016

Re: [akka-user] Re: Dedicated seed nodes for akka cluster

If you use auto-downing and that triggers because of a network partition there will be two separate clusters and they will not recombine automatically. That's why we recommend against using auto-downing and instead recommend something like the Split Brain Resolver http://doc.akka.io/docs/akka/rp-16

Re: [akka-user] Re: Can't get akka clustering to work in docker

Thanks for sharing, Eric tis 22 mars 2016 kl. 19:16 skrev Eric Swenson : > Hi Endre, > > I have read that part of the documentation, and after switching to a new > cassandra journal keyspace, everything is working as it should be. I've > confirmed that if I bump the "ECS Service" count to 2 (or g

Re: [akka-user] Dead letters during hand-over of cluster singleton actors

It's hard to tell from that info what is going on. Can you provide a minimized sample that can be used to reproduce the issue? /Patrik tis 29 mars 2016 kl. 13:54 skrev : > I have a 2-node akka cluster. Whenever a deployment happens, I send a > akka-cluster (the JMX tool) "leave" command to each

Re: [akka-user] postStop doesn't get invoked after actor initialization failure

> 2 apr 2016 kl. 10:31 skrev Guido Medina : > > I was only thinking in a consistent life cycle for both. > > With the new behavior I think I will never use preStart again in Akka Typed. > > That will be the only way we the users make sure we have control on > triggering conditions to execute p

Re: [akka-user] postStop doesn't get invoked after actor initialization failure

Created ticket 20205 . > 2 apr 2016 kl. 09:56 skrev Patrik Nordwall : > > +1 to changing in Akka Typed > -1 to changing untyped, or adding more hooks (the call chain is complicated > as is) > > /Patrik > fre 1 apr. 2016 kl. 14:44 skrev Guido Medina

Re: [akka-user] postStop doesn't get invoked after actor initialization failure

I was only thinking in a consistent life cycle for both. With the new behavior I think I will never use preStart again in Akka Typed. That will be the only way we the users make sure we have control on triggering conditions to execute postStop or not. Regards, Guido. -- >> Read

Re: [akka-user] postStop doesn't get invoked after actor initialization failure

+1 to changing in Akka Typed -1 to changing untyped, or adding more hooks (the call chain is complicated as is) /Patrik fre 1 apr. 2016 kl. 14:44 skrev Guido Medina : > And the order would be: > > *new instance* -> *preStart()* -> *postStop()* - if started -> > *preDestroy()* - if instantiated >

Re: [akka-user] [reactive-kafka 0.9.0.1] Why is my use of reactive-kafka so slow on commit?

There are examples in the readme to get you started. You should probably try batch commits. There are several examples of that (alternatives) in https://github.com/akka/reactive-kafka/blob/v0.11-M1/core/src/test/scala/examples/ConsumerExample.scala /Patrik lör 2 apr. 2016 kl. 00:35 skrev tigerfoo