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 deployment configuration. The reason I say it's a feature is because it's difficult to change without silent breakage. We actually use it in Akka itself to configure /system/IO-DNS/inet-address. There might be other such usages out there.
I regret that we didn't used the full path including /user prefix in the deployment configuration. Also difficult to change. Using "/**" is probably not a great idea anyway since it is very broad. I hope you can workaround the problem by defining a more specific wildcard. Regards, Patrik On Sat, Nov 12, 2016 at 4:28 PM, stella <[email protected]> wrote: > I'm playing with akka.actor.deployment configuration and found it > confusing. Assume that we have the following dispatcher: > > test-dispatcher{ > executor = "thread-pool-executor" > type = Dispatcher > } > > and we have two actors: */user/first* and */user/first/second* > > Now, if we set the deployment config as follows: > akka.actor.deployment{ > "/*" { > dispatcher = test-dispatcher > } > } > > In this case */user/first* well as all other actors will use the > dispatcher. I mean *deadLetters*, *logging*, etc... which would normally > be handled by *default-dispatcher*. */user/first/second * in turn uses > *default-dispatcher. * > > If we set > akka.actor.deployment{ > "/**" { > dispatcher = test-dispatcher > } > } > > then */user/first*, */user/first/second* as well as other system actors > will use the dispatcher. The documentation was not clear about that. They > said clearly in the documentation > <http://doc.akka.io/docs/akka/2.4/general/configuration.html#Actor_Deployment_Configuration> > : > >> The deployment section for a specific actor is defined by the path of the >> actor relative to */user* > > > So, system actor should have not been affected by the deployment > configuration. But they are... Is it a bug or I missed something? > > -- > >>>>>>>>>> Read the docs: http://akka.io/docs/ > >>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/ > current/additional/faq.html > >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user > --- > You received this message because you are subscribed to the Google Groups > "Akka User List" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/akka-user. > For more options, visit https://groups.google.com/d/optout. > -- Patrik Nordwall Akka Tech Lead Lightbend <http://www.lightbend.com/> - Reactive apps on the JVM Twitter: @patriknw -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
