You can use it on a single node, but you must still join that node to itself.
/Patrik sön 12 juni 2016 kl. 18:42 skrev kraythe <[email protected]>: > I am wondering if there is some problem since I am running Akka inside of > play 2.5 as an integrated environment. It would suck if thats a problem for > cluster config because that means I would have to separate the systems and > that just isnt happening any time soon, if at all. > > > On Friday, June 10, 2016 at 2:18:43 PM UTC-5, kraythe wrote: >> >> Greetings, >> >> I apologize if this has been asked but I am having what I assume is a >> config problem. When I start a single node I get the following logged >> errors and my sharded actors don't start. The errors are like such: >> >> 2016-06-10 14:07:01 -0500 - [INFO] - Message >> [akka.cluster.InternalClusterAction$InitJoin$] from >> Actor[akka://application/system/cluster/core/daemon/joinSeedNodeProcess-1#-956463865] >> to Actor[akka://application/deadLetters] was not delivered. [10] dead >> letters encountered, no more dead letters will be logged. This logging can >> be turned off or adjusted with configuration settings >> 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'. >> >> 2016-06-10 14:07:01 -0500 - [WARN] - Trying to register to coordinator at >> [None], but no acknowledgement. Total [368] buffered messages. >> >> 2016-06-10 14:07:03 -0500 - [WARN] - Trying to register to coordinator at >> [None], but no acknowledgement. Total [368] buffered messages. >> >> 2016-06-10 14:07:05 -0500 - [WARN] - Trying to register to coordinator at >> [None], but no acknowledgement. Total [368] buffered messages. >> 2016-06-10 14:07:06 -0500 - [WARN] - Association with remote system >> [akka.tcp://[email protected]:2551] has failed, address is now >> gated for [5000] ms. Reason: [Association failed with [akka.tcp:// >> [email protected]:2551]] Caused by: [Connection refused: / >> 127.0.0.1:2551]ere... >> >> As you can see there seems to be a problem starting sharding. So I >> checked my config and build.sbt and it seems to me I have my ducks in a >> row. Here is the akka.conf file (which is included by application.conf in a >> play2.5 app.) >> >> akka { >> >> log-dead-letters-during-shutdown = off >> extensions = [ >> "com.romix.akka.serialization.kryo.KryoSerializationExtension$", >> "akka.cluster.metrics.ClusterMetricsExtension" >> ] >> >> actor { >> provider = "akka.cluster.ClusterActorRefProvider" >> serializers { >> java = "akka.serialization.JavaSerializer" >> proto = "akka.remote.serialization.ProtobufSerializer" >> // FIXME define bindings in code for config. >> kryo = "com.romix.akka.serialization.kryo.KryoSerializer" >> } >> >> # See for Documentation: https://github.com/romix/akka-kryo-serialization >> kryo { >> type = "graph" >> idstrategy = "automatic" >> buffer-size = 4096 >> max-buffer-size = -1 >> use-manifests = false >> post-serialization-transformations = "off" >> kryo-custom-serializer-init = >> "distributed.serialization.SerializationConfigUtil" >> implicit-registration-logging = true >> kryo-trace = false >> } >> >> # default dispatcher used by Play >> default-dispatcher { >> # This will be used if you have set "executor = "fork-join-executor"" >> fork-join-executor { >> # Min number of threads to cap factor-based parallelism number to >> parallelism-min = 8 >> >> # The parallelism factor is used to determine thread pool size using >> the >> # following formula: ceil(available processors * factor). Resulting >> size >> # is then bounded by the parallelism-min and parallelism-max values. >> parallelism-factor = 4.0 >> >> # Max number of threads to cap factor-based parallelism number to >> parallelism-max = 64 >> >> # Setting to "FIFO" to use queue like peeking mode which "poll" or >> "LIFO" to use stack >> # like peeking mode which "pop". >> task-peeking-mode = "FIFO" >> } >> } >> } >> >> # See >> http://doc.akka.io/docs/akka/snapshot/general/configuration.html#config-akka-remote >> remote { >> log-remote-lifecycle-events = off >> enabled-transports = ["akka.remote.netty.tcp"] >> netty.tcp { >> # This causes the server to select a random available port in local >> mode and is important for running multiple >> # nodes on the same machine. It is overridden in environments. >> port = 0 >> } >> } >> >> cluster { >> // FIXME cant use static config! >> seed-nodes = [ >> "akka.tcp://[email protected]:2551" >> ] >> >> metrics { >> enabled = on >> native-library-extract-folder = ${user.dir}/target/native >> } >> >> # auto downing is NOT safe for production deployments. >> # you may want to use it during development, read more about it in the >> docs. >> # >> # auto-down-unreachable-after = 10s >> } >> >> akka { >> persistence { >> journal.plugin = "akka-persistence-sql-async.journal" >> snapshot-store.plugin = "akka-persistence-sql-async.snapshot-store" >> } >> } >> >> akka-persistence-sql-async { >> journal.class = >> "akka.persistence.journal.sqlasync.MySQLAsyncWriteJournal" >> snapshot-store.class = >> "akka.persistence.snapshot.sqlasync.MySQLSnapshotStore" >> >> user = ${db.default.username} >> password = ${db.default.password} >> url = ${db.default.url} >> max-pool-size = 4 >> wait-queue-capacity = 10000 >> >> metadata-table-name = "akka_persistence_metadata" >> journal-table-name = "akka_persistence_journal" >> snapshot-table-name = "akka_persistence_snapshots" >> } >> } >> >> >> And the build.sbt >> >> libraryDependencies ++= Seq( >> javaCore, >> javaJpa, >> javaJdbc, >> filters, >> cache, >> javaWs, >> // other dependencies omitted >> "com.typesafe.akka" % "akka-cluster_2.11" % "2.4.6", >> "com.typesafe.akka" % "akka-cluster-sharding_2.11" % "2.4.6", >> "com.typesafe.akka" % "akka-cluster-tools_2.11" % "2.4.6", >> "com.typesafe.akka" % "akka-cluster-metrics_2.11" % "2.4.6", >> // Used by akka-persistence >> "com.okumin" %% "akka-persistence-sql-async" % "0.3.1", >> "com.github.mauricio" %% "mysql-async" % "0.2.16" >> ) >> >> >> Any help would be appreciated. >> > -- > >>>>>>>>>> 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. > -- >>>>>>>>>> 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.
