You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: play-java-pekko-cluster-example/README.md
+7-7
Original file line number
Diff line number
Diff line change
@@ -67,15 +67,15 @@ In the terminals you should see activity like:
67
67
68
68
69
69
```
70
-
2020-09-01 11:40:45 INFO org.apache.pekko.cluster.Cluster Cluster(pekko://application) Cluster Node [pekko://[email protected]:25521] - Node [pekko://[email protected]:25521] is JOINING itself (with roles [dc-default]) and forming new cluster
71
-
2020-09-01 11:40:45 INFO org.apache.pekko.cluster.Cluster Cluster(pekko://application) Cluster Node [pekko://[email protected]:25521] - is the new leader among reachable nodes (more leaders may exist)
72
-
2020-09-01 11:40:45 INFO org.apache.pekko.cluster.Cluster Cluster(pekko://application) Cluster Node [pekko://[email protected]:25521] - Leader is moving node [pekko://[email protected]:25521] to [Up]
70
+
2020-09-01 11:40:45 INFO org.apache.pekko.cluster.Cluster Cluster(pekko://application) Cluster Node [pekko://[email protected]:73551] - Node [pekko://[email protected]:73551] is JOINING itself (with roles [dc-default]) and forming new cluster
71
+
2020-09-01 11:40:45 INFO org.apache.pekko.cluster.Cluster Cluster(pekko://application) Cluster Node [pekko://[email protected]:73551] - is the new leader among reachable nodes (more leaders may exist)
72
+
2020-09-01 11:40:45 INFO org.apache.pekko.cluster.Cluster Cluster(pekko://application) Cluster Node [pekko://[email protected]:73551] - Leader is moving node [pekko://[email protected]:73551] to [Up]
73
73
```
74
74
75
-
The logs above indicate node 1 (identified as `pekko://[email protected]:25521`) and node 2 (identified as `pekko://[email protected]:25522
76
-
`) have seen each other and established a connection, then `pekko://[email protected]:25521` became the leader and that leader decided to mark
77
-
`pekko://[email protected]:25521`'s status as `Up`. Finally, the singleton `counter-actor` that we use on this sample app is available. You
78
-
should also see, in the logs, how the node 3 (identified as `pekko://[email protected]:25523`) also joins the cluster.
75
+
The logs above indicate node 1 (identified as `pekko://[email protected]:73551`) and node 2 (identified as `pekko://[email protected]:73552
76
+
`) have seen each other and established a connection, then `pekko://[email protected]:73551` became the leader and that leader decided to mark
77
+
`pekko://[email protected]:73551`'s status as `Up`. Finally, the singleton `counter-actor` that we use on this sample app is available. You
78
+
should also see, in the logs, how the node 3 (identified as `pekko://[email protected]:73553`) also joins the cluster.
79
79
80
80
Finally, open three browser tabs to the URLs http://localhost:9001/, http://localhost:9002/, and http://localhost:9003/ (each points to a different
81
81
Play instance) and interact with the UI. Note how all three increment a single counter in the singleton.
0 commit comments