[akka-user] Is there a way to reload configuration at run time?

Is there a way to reload configuration at run time? For example: I defined failure detect parameter "monitored-by-nr-of-members = 1" while the cluster consists of 3 nodes. I want to adjustment "monitored-by-nr-of-members = 5" after some new nodes have been joined to the cluster. Thanks. --

Re: [akka-user] Re: Akka Cluster Across Datacenters

I'm not particularly surprised by this, but I'm curious: do you know if anyone has done any serious work on Akka "meta-clusters" for situations like this? For example, while it's certainly at least a few years off, I should *probably* eventually distribute my Cluster Sharding geographically,

Re: [akka-user] Do we rename the actor instance's name.

The system certainly doesn't do so normally; I don't *think* it's possible to, although I'm not the expert. Why do you ask? On Thu, Aug 11, 2016 at 6:41 AM, Vishal Singh wrote: > Hi All, > > Once we have created an actor instance, do we change name of it later. > >

Re: [akka-user] Errors using Partition for custom FanOutShape

Thanks for your reply Johan. I can't explain it, but now it's working for me and the error is gone. I have no idea what changed, but things seem to be working now. Thanks again for your time! --Eric On Thursday, August 11, 2016 at 3:57:58 AM UTC-6, Akka Team wrote: > > The sample code does

Re: [akka-user] Re: Akka cluster node shutting down in the middle of processing requests

I have not looked at the logs but you find answer to your last question in http://doc.akka.io/docs/akka/2.4/scala/cluster-usage.html#How_To_Cleanup_when_Member_is_Removed /Patrik fre 5 aug. 2016 kl. 22:31 skrev Eric Swenson : > One more clue as to the cluster daemon's shutting

Re: [akka-user] Hot Standby Persistent Actor - https://github.com/akka/akka/issues/13938

The milestone of an issue is no guarantee that it will be released in that version, until the issue is closed. We can't do that kind of planning. This would be a great feature for community contibution. Queries are there now. /Patrik ons 10 aug. 2016 kl. 07:04 skrev Muthukumaran Kothandaraman <

Re: [akka-user] Re: Akka Cluster Across Datacenters

I agree with Ryan that it's generally not recommended. I would like to add that the cluster membership and distributed data will work pretty fine across DC thanks to their gossip based protocols, but there are other tools, such as cluster sharding, that are not a good fit for it. Cluster downing

[akka-user] Re: Akka Cluster Across Datacenters

Akka is generally not recommended for spanning data centers. I would consider the cluster client, though personally I'd probably choose Kafka for this role, with separate clusters in each DC. IME cross-DC communication is generally a scenario where you really want to make sure messages are

[akka-user] [akka-streams] Accessing the dispatcher used for a mapAsync stage

Hello everyone, Is there a canonical way of accessing the dispatcher/ExecutionContext used for a mapAsync stage? I would like to use the monadic combinators on a future within my mapAsync stage, and these require an implicit ExecutionContext. Contrived example: ``` def myFlow =

[akka-user] Akka Cluster Across Datacenters

I am writing a system that needs to be distributed across various data centers e.g. US, Europe, Asia. I need to replicate a small amount of configuration data between the nodes in each datacenter (there are a small number of nodes in each data center, 1 or 2) and this configuration can be

[akka-user] What happened if leader become unreachable in the cluster

Does the leader will down himself or another node will become leader? Where is the code about this in the source files. Thanks much for your help! -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >>

[akka-user] Do we rename the actor instance's name.

Hi All, Once we have created an actor instance, do we change name of it later. Thanks. -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >> http://doc.akka.io/docs/akka/current/additional/faq.html >> Search the archives:

Re: [akka-user] Errors using Partition for custom FanOutShape

The sample code does not contain a Broadcast, but your error message does, so I can't see how the source you showed would give that error. This little sample works nicely as expected: Source source = Source.from(Arrays.asList(0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10)); final

Re: [akka-user] How to create listener which is placed outside actor system?

Isn't what you want is a simple actor that calls the callback? I.e.: class CallbackActor(callback: Callback) extends Actor { ... def receive = { case msg: MessageA => callback.invoke(msg) } ... } ... callbackInvoker = system.actorOf(callbackActorProps, ...) callbackInvoker ! new

Re: [akka-user] How to create listener which is placed outside actor system?

I'm not sure I understand. Perhaps if you outline your requirements (i.e. how modules are required to interact etc) it will be easier for others to suggest possible solutions? On Wed, Aug 10, 2016 at 8:53 PM, Иван Осипов wrote: > Only one module of my application

Re: [akka-user] Streams - custom HTTP POST Sink?

On Thu, Aug 11, 2016 at 12:32 AM, Mike Bryant wrote: > Thanks Endre - that's perfect. The prefixAndTail with zero prefix was the > missing ingredient I needed to transform the whole source within a separate > flow (maybe there's a case for adding that as another specific >

Re: [akka-user] Streams - custom HTTP POST Sink?

Thanks Endre - that's perfect. The prefixAndTail with zero prefix was the missing ingredient I needed to transform the whole source within a separate flow (maybe there's a case for adding that as another specific "mapSource"-type method?). Best, ~Mike On Wednesday, 10 August 2016 22:20:58