This channel is available for all Akka enthusiasts—newbies as well as gurus—for the exchange of knowledge and the coordination of efforts around Akka. For more info see: http://bit.ly/akka-gitter
I have a question. Why 'akka-discovery-aws-api' doesn't require 'akka.remote.artery' configs but 'akka.discovery' does? Can I ask where the omitting part happens in 'https://github.com/akka/akka-management'?
akka-discovery-aws-api works with just
discovery {
method = aws-api-ec2-tag-based
aws-api-ec2-tag-based {
filters = "tag:mycomponent=my service name"
}}
management {
cluster.bootstrap {
contact-point-discovery {
service-name = "my service name"
discovery-method = aws-api-ec2-tag-based
} } }https://mvnrepository.com/artifact/com.lightbend.akka.discovery/akka-discovery-aws-api_2.12/1.0.5
seed-nodes = []
seed-nodes = ${?SEED_NODES}
roles = ["seed", "worker", "S3Sharding", "GCSSharding"]
role {
seed.min-nr-of-members = 1
}
sharding.state-store-mode = ddata
sharding.remember-entities = on
sharding.distributed-data.durable.keys = []
sharding.passivate-idle-entity-after = off
downing-provider-class = "tanukki.akka.cluster.autodown.MajorityLeaderAutoDowning"
use-dispatcher = akka.cluster-dispatcher
failure-detector {
heartbeat-interval = 1 s
threshold = 15.0
min-std-deviation = 200 ms
acceptable-heartbeat-pause = 300 s
expected-response-after = 300 s
monitored-by-nr-of-members = 3
}
}
2.6.1 is out :tada: https://akka.io/blog/news/2019/12/06/akka-2.6.1-released
Thank you for releasing a new version !
I will try to explain the scenario, when application start on one port (say 2551) it run successfully. But when new port (say 2552) join the cluster then cluster with role, start failing and showing up with this
[backend-cluster-ingestion-7fbcb5497f-qnkw7] 15:49:30.233 [backend-cluster-akka.actor.default-dispatcher-76] WARN akka.cluster.sharding.ShardRegion - scheduler-27: Trying to register to coordinator at [ActorSelection[Anchor(akka.tcp://backend-cluster@10.2.136.10:2551/), Path(/system/sharding/scheduler-27-Coordinator/singleton/coordinator)]], but no acknowledgement. Total [30750] buffered messages. [Coordinator [Member(address = akka.tcp://backend-cluster@10.2.136.10:2551, status = Up)] is reachable.]
Hi, I have been using 'akka distributed' data with 'akka-discovery-aws-api' (akka 2.5.23 & management 1.0.3). It has been running fine in production with minimum setting. I upgraded to akka 2.6.0. It seems I need to specify akka.remote.artery {enabled, port} explicitly. I then encountered the following error. I have no idea what to do.
Caused by: com.typesafe.config.ConfigException$Missing: application.test.conf @ jar:file:/usr/lib/..........jar!/application.test.conf: 70: No configuration setting found for key 'large-message-destinations''I guess I now need to specify 'large-message-destinations'. I don't understand why I need to manually set these.
I read 'https://doc.akka.io/docs/akka/current/remoting-artery.html#dedicated-subchannel-for-large-messages' but I have no idea of granualty of this setting (given that I use akka-distributed-data)
I expect that 'akka-management-clusterbootstrap' & 'akka-discovery-aws-api' would handle such settings automatically. It doesn't look like it does.
Any advice?
(path(Segment) & get { cars => docs: https://doc.akka.io/docs/akka-http/current/routing-dsl/path-matchers.html#the-pathmatcher-dsl example usage https://github.com/akka/akka-samples/blob/2.6/akka-sample-sharding-scala/killrweather/src/main/scala/sample/killrweather/WeatherRoutes.scala#L51
