sadekmunawar opened a new pull request, #1562: URL: https://github.com/apache/pekko/pull/1562
This bug causes major issues when a cluster contains nodes using both "akka" and "pekko". It can be a significant obstacle when migrating from Akka to Pekko through a rolling upgrade, especially if the migration requires the cluster to run with mixed protocols for an extended period. Due to this bug, the DistributedPubSubMediator fails to send messages to some registered nodes. In the DistributedPubSubMediator, node addresses are stored in a [set](https://code.amazon.com/packages/PekkoClusterTools/blobs/697135892e22f31922167fd1faa102b9fbb49c56/--/src/main/scala/org/apache/pekko/cluster/pubsub/DistributedPubSubMediator.scala#L598). However, when [set membership ](https://github.com/scala/scala/blob/a5270194b6eec9678a79e2f88a83d83aa6b92de1/src/library/scala/collection/immutable/RedBlackTree.scala#L47C1-L59C4) relies on the faulty addressOrdering method, set.contains returns false for some addresses that are actually in the set. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
