-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Closed
Labels
1 - triagedTickets that are safe to pick up for contributing in terms of likeliness of being acceptedTickets that are safe to pick up for contributing in terms of likeliness of being accepted2 - pick nextUsed to mark issues which are next up in the queue to be worked on. The tag is non-bindingUsed to mark issues which are next up in the queue to be worked on. The tag is non-bindinghelp wantedIssues that the core team will likely not have time to work onIssues that the core team will likely not have time to work ont:cluster-tools
Milestone
Description
When starting an application that uses Akka Cluster Sharding, if no cluster has been joined (e.g., because of forgotten seed node configuration) there is a cryptic error message:
Trying to register to coordinator at [None], but no acknowledgement.
This doesn't communicate the underlying issue, which is usually a misconfiguration.
Reproduction
- Clone the akka-samples repo and
cd
toakka-sample-sharding-scala
- Edit
src/main/resources/application.conf
and delete theseed-nodes
setting - sbt "runMain sample.sharding.ShardingApp 2551"
- It logs an INFO-level message saying "Cluster Node [akka.tcp://ShardingSystem@127.0.0.1:2551] - No seed-nodes configured, manual cluster join required", but because the application continues normally and the message is at INFO level, it is easy to miss this.
- Eventually, you will begin to see "Trying to register to coordinator at [None], but no acknowledgement." warnings logged. It isn't clear that this is connected to the fact that the actor system hasn't joined a cluster.
References
- https://groups.google.com/d/topic/akka-user/VDsHEM2Sxx0/discussion
- https://groups.google.com/d/topic/akka-user/Qf5b9ii4-Z4/discussion
- https://groups.google.com/d/topic/akka-user/JOQLWAI8Zvc/discussion
- Service startup is incomplete if using JDBC Persistent Entities in standalone / production mode lagom/lagom#500
Metadata
Metadata
Assignees
Labels
1 - triagedTickets that are safe to pick up for contributing in terms of likeliness of being acceptedTickets that are safe to pick up for contributing in terms of likeliness of being accepted2 - pick nextUsed to mark issues which are next up in the queue to be worked on. The tag is non-bindingUsed to mark issues which are next up in the queue to be worked on. The tag is non-bindinghelp wantedIssues that the core team will likely not have time to work onIssues that the core team will likely not have time to work ont:cluster-tools