Re: [akka-user] how to use cluster client and cluster sharding together

UPDATE: It's /system/sharding/NAME now четверг, 6 марта 2014 г., 21:03:40 UTC+4 пользователь Patrik Nordwall написал: > > Hi, > > > On Thu, Mar 6, 2014 at 12:09 PM, Xingrun CHEN > wrote: > >> To use cluster client, I must register service on server nodes >> as receptionist

Re: [akka-user] Re: Trying to load configurations

Hi, it looks like you are not passing your custom parsed and loaded configuration to actor system constructor: ActorSystem(_configName). On Thu, Jun 9, 2016 at 10:05 PM, Ian Nowland wrote: > Further investigation has shown me that the same configurations, added to > my

Re: [akka-user] Cluster Sharding(2.4, Java/Groovy)-how to avoid a rebalance during a rolling release?

Hi, you can provide a custom shard allocation strategy that during rolling release returns empty set of shards that need to be rebalanced. On Fri, Jun 17, 2016 at 10:21 PM, Michael Kohout

Re: [akka-user] Best way to deal with Actors that integrate other Actor Data?

Hi, in the short term actor situation that you described (these are sometimes also called per-request actors), you can send to the short term actor something, that lets you complete the original request that arrived to the endpoint. I do not know what you are using for handling requests, but

[akka-user] Re: DistributedPubSub keeps sending to exited nodes

Ok, my assumption is right (see https://github.com/akka/akka/blob/master/akka-cluster-tools/src/main/scala/akka/cluster/pubsub/DistributedPubSubMediator.scala#L669). Is there a way to work around this? I don't want to wait some random time interval after leaving before actually shutting down.

[akka-user] DistributedPubSub keeps sending to exited nodes

Hi, I have a sample application where two nodes join an Akka cluster. On both nodes there is an actor running registered to DistributedPubSubMediator and both are sending a Ping once per second (that hits either itself or the other node). Then I gracefully shut down Node B (leave cluster,

[akka-user] Re: [akka-stream] Concatenate multiple Sources while preserving materialized values

Sorry, this is actually supported and very straightforward. Solution is: //most common Keep.left case source1.concat(source2) //more general source1.concatMat(source2)(Keep.both) //or whatever strategy On Thursday, June 23, 2016 at 2:55:11 PM UTC-4, Arron Norwell wrote: > > Hi, > > I'm looking

[akka-user] [akka-stream] Concatenate multiple Sources while preserving materialized values

Hi, I'm looking for a good way to concatenate sources while preserving materialized values. For example, If I have val source1: Source[T,Mat] = _ val source2: Source[T,akka.NotUsed] = _ I would like to be able to preserve the first materialized value (and possibly more generally, support other

[akka-user] Actor stream to file

I have a stream which needs to output some progress/error text to a file and to console (different things to each). I've implemented something using alsoTo(fileSink).alsoTo(consoleSink). But now I'm considering funneling these messages through an actor intermediary instead. i.e.

[akka-user] Re: Persistence/CQRS: Persisting events without recovery

I completely missed that, thanks! I would still rather have a way to persist arbitrary events without actors, but disabling the recovery also works. Thanks, Tal On Thursday, June 23, 2016 at 3:21:31 PM UTC+3, Mark Hatton wrote: > > I apply the very same pattern in a couple of services. The

[akka-user] Re: At-least once delivery and the ActorPath (Java examples)

For reference - and having conducted a lot of testing on various situations. Both patterns would work - either delivering to a delegate actor that you have just created, or delivering to a fixed path - such as a cluster sharding location. There is a benefit to the latter - in that during

[akka-user] Akka streams. Handling exceptions

Hi there. I have a question - how to correct handle exceptions using akka streams in follow situation. Situation: 1) get data using tcp io 2) collect and validate a message 3) send the message to db but there can be timeout exception if db is not available and by business I need to send

Re: [akka-user] Re: Akka Cluster : Association with remote system has failed

Hi Patrik, Thank you very much for your reply. I enabled the Akka remote logging and ran both of my nodes. Attached here the logs for your perusal. Any findings/pointers are highly appreciated. On Tuesday, 21 June 2016 12:36:10 UTC-7, Patrik Nordwall wrote: > > Try to run with the remote debug