-
Notifications
You must be signed in to change notification settings - Fork 186
reimplement fix for akka/pekko cluster #1594
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
My changes have fixed most tests but the new ones in this PR are still broken. It looks like we need more changes in org.apache.pekko.remote.Remoting$.localAddressForRemote. |
|
@raboof @He-Pin @sadekmunawar I think I have all the tests passing now. I will check again later. If these changes are approved, I can remove the temp change to run the nightly tests during CI build of this PR. #1610 raised for a flaky test |
|
I have not look into the details, but will it replay the akka node with akka protocol ?otherwise, it will not work. can a akka node sending ping-pong after joined? And there are akka.tcp and akka protocols, which should be tested too. |
| pekko.coordinated-shutdown.terminate-actor-system = on | ||
| pekko.remote.classic.netty.tcp.port = 0 | ||
| pekko.remote.artery.canonical.port = 0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we need test both pekko.tcp and pekko, I mean both artery and classical transports, seems this only test one.
52a1769 to
1303acd
Compare
|
Looks reasonable to me. |
|
I changed the PR tests to include some cluster tests as per #1591 |
| fail-fast: false | ||
| matrix: | ||
| command: | ||
| - cluster/test distributed-data/test cluster-tools/test cluster-metrics/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
need sbt cluster/MultiJvm/test too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#1592 covers that. It looks like running the multiJvm tests will be more complicated. The aim of this small change is that the test modified in this PR runs in the PR CI - because at the momemt, it does not.
This reverts commit 7af03e5.
91f1024 to
638ecf5
Compare
He-Pin
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great!
lgtm, it covers pekko join akka and akka join pekko.
* Revert "revert apache#1568 due to test failures (apache#1587)" This reverts commit 7af03e5. * temp run nightly test in this PR * no need for square brackets because the set print adds them * logging to find issue * support tcp protocols * Update ClusterDaemon.scala * remove temp logging * try to fix issue in Remoting * extra tests * more tests * ignore udp tests * try to make tests tidy up after failures * Update MixedProtocolClusterSpec.scala * Update MixedProtocolClusterSpec.scala * run main cluster tests for PR
* Revert "revert #1568 due to test failures (#1587)" This reverts commit 7af03e5. * temp run nightly test in this PR * no need for square brackets because the set print adds them * logging to find issue * support tcp protocols * Update ClusterDaemon.scala * remove temp logging * try to fix issue in Remoting * extra tests * more tests * ignore udp tests * try to make tests tidy up after failures * Update MixedProtocolClusterSpec.scala * Update MixedProtocolClusterSpec.scala * run main cluster tests for PR
Run I the tests locally they pass but the nightly tests were failing until I removed this change.
see #1590