regiskuckaertz opened a new issue, #1854:
URL: https://github.com/apache/pekko/issues/1854
Hello 👋 while migrating a cluster that is still using classic remoting, I
came across a blocker. Here's the config:
```
pekko {
cluster {
seed-nodes = [ "akka.ssl.tcp://node1", "akka.ssl.tcp://node2" ]
}
remote {
artery.enabled = false
accept-protocol-names = ["pekko", "akka"]
protocol-name = "akka"
classic {
enabled-transports = ["pekko.remote.classic.netty.ssl"]
netty.ssl { ... }
}
}
}
```
At startup, the cluster fails to start immediately, rejecting the protocol
"akka.ssl.tcp" because only "akka.tcp" and "pekko.tcp" are valid. There's a few
references to "pekko.ssl.tcp" in the documentation but not much so I wonder if
maybe there is something missing.
I think the issue starts here:
https://github.com/apache/pekko/blob/e308cf5e10e0614a7e887e90ce15dbdc3332ff97/remote/src/main/scala/org/apache/pekko/remote/RemoteSettings.scala#L213-L225
which is used in the cluster daemon to join members (I have also seen rejected
members due to unaccepted protocols when I changed the seed nodes protocol to
"akka.tcp" for testing). Maybe somewhere there should be a check to see if at
least one enabled transport has `enable-ssl` turned on, and if yes then
`{protocolName}.ssl.tcp` should be accepted? I'm not sure what the
repercussions would be.
--
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: notifications-unsubscr...@pekko.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@pekko.apache.org
For additional commands, e-mail: notifications-h...@pekko.apache.org
