You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@pekko.apache.org by "regiskuckaertz (via GitHub)" <gi...@apache.org> on 2025/05/20 07:21:20 UTC
[I] Seed nodes in a cluster using classic remoting [pekko]
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-unsubscribe@pekko.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [I] Seed nodes in a cluster using classic remoting [pekko]
Posted by "regiskuckaertz (via GitHub)" <gi...@apache.org>.
regiskuckaertz commented on issue #1854:
URL: https://github.com/apache/pekko/issues/1854#issuecomment-2904792790
yay 🕺 thanks all for your commitment
--
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-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [I] Seed nodes in a cluster using classic remoting [pekko]
Posted by "pjfanning (via GitHub)" <gi...@apache.org>.
pjfanning commented on issue #1854:
URL: https://github.com/apache/pekko/issues/1854#issuecomment-2906677490
@regiskuckaertz you are right about the joining node sending a fragment of its own config. This is probably what is wrong here. I thought that Pekko might have had code to modify that config before checking it (by replacing the akka with pekko) but maybe that is not there or has a flaw. I will look into this. In the mean time, you would be best to disable the join check.
--
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-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [I] Seed nodes in a cluster using classic remoting [pekko]
Posted by "raboof (via GitHub)" <gi...@apache.org>.
raboof commented on issue #1854:
URL: https://github.com/apache/pekko/issues/1854#issuecomment-2900165817
triggered
--
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-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [I] Seed nodes in a cluster using classic remoting [pekko]
Posted by "regiskuckaertz (via GitHub)" <gi...@apache.org>.
regiskuckaertz commented on issue #1854:
URL: https://github.com/apache/pekko/issues/1854#issuecomment-2900097086
Ouch, looks like maven timed out, would it be possible to relaunch the job? https://github.com/apache/pekko/actions/runs/15175219565/job/42674110770
--
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-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [I] Seed nodes in a cluster using classic remoting [pekko]
Posted by "pjfanning (via GitHub)" <gi...@apache.org>.
pjfanning commented on issue #1854:
URL: https://github.com/apache/pekko/issues/1854#issuecomment-2894422176
also seeing
```
[ERROR] [05/20/2025 14:27:02.954] [MixedProtocolClusterSpec-pekko.actor.internal-dispatcher-4] [org.apache.pekko.cluster.ClusterActorRefProvider] No root guardian at [akka.ssl.tcp://MixedProtocolClusterSpec@192.168.0.2:62752]
org.apache.pekko.remote.RemoteTransportException: No transport is loaded for protocol: [akka.ssl.tcp], available protocols: [akka.tcp, pekko.tcp]
at org.apache.pekko.remote.Remoting$.localAddressForRemote(Remoting.scala:125
at org.apache.pekko.remote.Remoting.localAddressForRemote(Remoting.scala:168)
at org.apache.pekko.remote.RemoteActorRefProvider.rootGuardianAt(RemoteActorRefProvider.scala:488)
at org.apache.pekko.actor.ActorRefFactory.actorSelection(ActorRefProvider.scala:261)
at org.apache.pekko.actor.ActorRefFactory.actorSelection$(ActorRefProvider.scala:255)
at org.apache.pekko.actor.ActorCell.actorSelection(ActorCell.scala:420)
at org.apache.pekko.cluster.SeedNodeProcess.$anonfun$receiveJoinSeedNode$1(SeedNodeProcess.scala:88)
at org.apache.pekko.cluster.SeedNodeProcess.$anonfun$receiveJoinSeedNode$1$adapted(SeedNodeProcess.scala:87)
at scala.collection.immutable.Set$Set1.foreach(Set.scala:177)
at org.apache.pekko.cluster.SeedNodeProcess.receiveJoinSeedNode(SeedNodeProcess.scala:87)
at org.apache.pekko.cluster.JoinSeedNodeProcess$$anonfun$receive$2.applyOrElse(SeedNodeProcess.scala:299)
```
--
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-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [I] Seed nodes in a cluster using classic remoting [pekko]
Posted by "regiskuckaertz (via GitHub)" <gi...@apache.org>.
regiskuckaertz closed issue #1854: Seed nodes in a cluster using classic remoting
URL: https://github.com/apache/pekko/issues/1854
--
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-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [I] Seed nodes in a cluster using classic remoting [pekko]
Posted by "regiskuckaertz (via GitHub)" <gi...@apache.org>.
regiskuckaertz commented on issue #1854:
URL: https://github.com/apache/pekko/issues/1854#issuecomment-2900514098
sorry to be the bearer of bad news, it seems GH bailed out after 53m 😭
--
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-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [I] Seed nodes in a cluster using classic remoting [pekko]
Posted by "regiskuckaertz (via GitHub)" <gi...@apache.org>.
regiskuckaertz commented on issue #1854:
URL: https://github.com/apache/pekko/issues/1854#issuecomment-2980435768
@pjfanning thanks again, I just tested with 1.1.4 a heterogeneous cluster and it worked like a charm 🕺
--
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-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [I] Seed nodes in a cluster using classic remoting [pekko]
Posted by "pjfanning (via GitHub)" <gi...@apache.org>.
pjfanning commented on issue #1854:
URL: https://github.com/apache/pekko/issues/1854#issuecomment-2894377217
I'm working on a test case and am getting a warning like this:
```
[WARN] [05/20/2025 14:11:21.255] [MixedProtocolClusterSpec-pekko.actor.internal-dispatcher-11] [Cluster(pekko://MixedProtocolClusterSpec)] Cluster Node [pekko.ssl.tcp://MixedProtocolClusterSpec@192.168.0.2:62635] - Trying to join member with wrong protocol, but was ignored, expected any of Set(pekko, akka, pekko.tcp, akka.tcp) but was [pekko.ssl.tcp]
```
https://github.com/apache/pekko/blob/f9052401143c8e056c14d1c62e6a695e961b842a/cluster/src/main/scala/org/apache/pekko/cluster/ClusterDaemon.scala#L711
--
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-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [I] Seed nodes in a cluster using classic remoting [pekko]
Posted by "regiskuckaertz (via GitHub)" <gi...@apache.org>.
regiskuckaertz commented on issue #1854:
URL: https://github.com/apache/pekko/issues/1854#issuecomment-2906506597
That's what I thought at first, but reading through the code my understanding is that a joining node [sends its own configuration](https://github.com/apache/pekko/blob/9ab68569653dc40c794349da53060d11f324b2fa/cluster/src/main/scala/org/apache/pekko/cluster/ClusterDaemon.scala#L576) which for an akka node will be `akka.*`, so that would explain why the check fails. But I will triple-check that our assembly rules did not mess up anything, we have some esoteric configuration logic based on the environment which could be simplified a little bit.
--
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-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [I] Seed nodes in a cluster using classic remoting [pekko]
Posted by "pjfanning (via GitHub)" <gi...@apache.org>.
pjfanning commented on issue #1854:
URL: https://github.com/apache/pekko/issues/1854#issuecomment-2905304394
You could disable the compatibility check. In theory, you shouldn't need to but it makes like a bit simpler in a secure network to disable it in this case.
The line that is failing seems to be a lookup of the config `pekko.cluster.downing-provider-class`. There is a default setting for that in the reference.conf of pekko-cluster.jar which is the same jar that the JoinConfigCompatCheckCluster class is in.
Is there a chance that you are not using the pekko jars directly but are doing some sort of bundling them that might mangle the reference.conf files in the jars?
--
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-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [I] Seed nodes in a cluster using classic remoting [pekko]
Posted by "regiskuckaertz (via GitHub)" <gi...@apache.org>.
regiskuckaertz commented on issue #1854:
URL: https://github.com/apache/pekko/issues/1854#issuecomment-2905132800
ok, it's starting up 🎉 I'm getting an exception when an akka node is trying to join, I have a feeling I made a mistake somewhere so I'm following the thread. However just in case it rings a bell, here it is:
```
2025-05-23 16:41:24,064 INFO [PTS-pekko.actor.default-dispatcher-22] org.apache.pekko.cluster.Cluster Cluster(pekko://PTS) - Cluster Node [akka.ssl.tcp://PTS@***:1600] - Received InitJoinAck message from [Actor[akka.ssl.tcp://PTS@***:1601/system/cluster/core/daemon#-1262355348]] to [akka.ssl.tcp://PTS@***:1600]
2025-05-23 16:41:24,064 ERROR [PTS-pekko.actor.default-dispatcher-22] o.a.pekko.actor.OneForOneStrategy pekko://PTS/system/cluster/core/daemon/firstSeedNodeProcess-1 - String: 1: No configuration setting found for key 'pekko'
com.typesafe.config.ConfigException$Missing: String: 1: No configuration setting found for key 'pekko'
at com.typesafe.config.impl.SimpleConfig.findKeyOrNull(SimpleConfig.java:157)
at com.typesafe.config.impl.SimpleConfig.findKey(SimpleConfig.java:150)
at com.typesafe.config.impl.SimpleConfig.findOrNull(SimpleConfig.java:177)
at com.typesafe.config.impl.SimpleConfig.find(SimpleConfig.java:189)
at com.typesafe.config.impl.SimpleConfig.find(SimpleConfig.java:194)
at com.typesafe.config.impl.SimpleConfig.getString(SimpleConfig.java:251)
at org.apache.pekko.cluster.JoinConfigCompatCheckCluster.check(JoinConfigCompatCheckCluster.scala:41)
at org.apache.pekko.cluster.JoinConfigCompatChecker$$anon$1.$anonfun$check$1(JoinConfigCompatChecker.scala:169)
at scala.collection.IterableOnceOps.foldLeft(IterableOnce.scala:676)
at scala.collection.IterableOnceOps.foldLeft$(IterableOnce.scala:670)
at scala.collection.AbstractIterable.foldLeft(Iterable.scala:933)
at org.apache.pekko.cluster.JoinConfigCompatChecker$$anon$1.check(JoinConfigCompatChecker.scala:168)
at org.apache.pekko.cluster.SeedNodeProcess.receiveInitJoinAckCompatibleConfig(SeedNodeProcess.scala:134)
at org.apache.pekko.cluster.FirstSeedNodeProcess$$anonfun$receive$1.applyOrElse(SeedNodeProcess.scala:230)
at org.apache.pekko.actor.Actor.aroundReceive(Actor.scala:547)
at org.apache.pekko.actor.Actor.aroundReceive$(Actor.scala:545)
at org.apache.pekko.cluster.SeedNodeProcess.aroundReceive(SeedNodeProcess.scala:28)
at org.apache.pekko.actor.ActorCell.receiveMessage(ActorCell.scala:590)
at org.apache.pekko.actor.ActorCell.invoke(ActorCell.scala:557)
at org.apache.pekko.dispatch.Mailbox.processMailbox(Mailbox.scala:272)
at org.apache.pekko.dispatch.Mailbox.run(Mailbox.scala:233)
at org.apache.pekko.dispatch.Mailbox.exec(Mailbox.scala:245)
at java.base/java.util.concurrent.ForkJoinTask.doExec(Unknown Source)
at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(Unknown Source)
at java.base/java.util.concurrent.ForkJoinPool.scan(Unknown Source)
at java.base/java.util.concurrent.ForkJoinPool.runWorker(Unknown Source)
at java.base/java.util.concurrent.ForkJoinWorkerThread.run(Unknown Source)
```
Should this check be disabled in a heterogenous cluster?
```
pekko.cluster.configuration-compatibility-check.enforce-on-join = no
```
... or perhaps create a new check that accounts for `akka.*` config?
```
pekko.cluster.configuration-compatibility-check.checkers.pekko-cluster = "JoinAkkaConfigCompatCheckCluster"
```
--
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-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [I] Seed nodes in a cluster using classic remoting [pekko]
Posted by "regiskuckaertz (via GitHub)" <gi...@apache.org>.
regiskuckaertz commented on issue #1854:
URL: https://github.com/apache/pekko/issues/1854#issuecomment-2894431827
hi @pjfanning wow thanks for picking up so quickly 🙇 Yes that is exactly what I am getting too
--
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-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [I] Seed nodes in a cluster using classic remoting [pekko]
Posted by "pjfanning (via GitHub)" <gi...@apache.org>.
pjfanning commented on issue #1854:
URL: https://github.com/apache/pekko/issues/1854#issuecomment-2895536219
@regiskuckaertz when the PR gets merged, the nightly build should produce a snapshot jar. I can comment with the details when it's ready.
--
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-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [I] Seed nodes in a cluster using classic remoting [pekko]
Posted by "pjfanning (via GitHub)" <gi...@apache.org>.
pjfanning commented on issue #1854:
URL: https://github.com/apache/pekko/issues/1854#issuecomment-2904711058
* 1.1.3+9-06e62c39-SNAPSHOT is published with the changes
* you'll need to add a resolver in your build tool to access the repository.apache.org snapshots repo - https://pekko.apache.org/docs/pekko/current/project/links.html#snapshots-repository
--
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-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [I] Seed nodes in a cluster using classic remoting [pekko]
Posted by "regiskuckaertz (via GitHub)" <gi...@apache.org>.
regiskuckaertz commented on issue #1854:
URL: https://github.com/apache/pekko/issues/1854#issuecomment-2895374559
@pjfanning there must not be many clusters using Classic anymore 😅 glad I helped discover an issue, is there anything I can help with like testing from a snapshot?
--
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-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [I] Seed nodes in a cluster using classic remoting [pekko]
Posted by "pjfanning (via GitHub)" <gi...@apache.org>.
pjfanning commented on issue #1854:
URL: https://github.com/apache/pekko/issues/1854#issuecomment-2900518281
There is something up with the ASF Nexus server the last few days. We're seeing issues publishing jars across all our modules.
--
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-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [I] Seed nodes in a cluster using classic remoting [pekko]
Posted by "pjfanning (via GitHub)" <gi...@apache.org>.
pjfanning commented on issue #1854:
URL: https://github.com/apache/pekko/issues/1854#issuecomment-2980458113
> [@pjfanning](https://github.com/pjfanning) thanks again, I just tested with 1.1.4 a heterogeneous cluster and it worked like a charm 🕺
Thanks @regiskuckaertz for testing this and helping us to debug the issues.
--
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-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [I] Seed nodes in a cluster using classic remoting [pekko]
Posted by "pjfanning (via GitHub)" <gi...@apache.org>.
pjfanning commented on issue #1854:
URL: https://github.com/apache/pekko/issues/1854#issuecomment-2894947294
@regiskuckaertz in my testing of #1857, it looks like we may have broken support for classic remoting using SSL/TLS altogether. The changes in #1857 appear to fix this and to also fix the issues with forming mixed Akka/Pekko clusters with classic remoting using SSL/TLS.
--
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-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [I] Seed nodes in a cluster using classic remoting [pekko]
Posted by "pjfanning (via GitHub)" <gi...@apache.org>.
pjfanning commented on issue #1854:
URL: https://github.com/apache/pekko/issues/1854#issuecomment-2893697468
@regiskuckaertz would you have logs or stack traces? This would help us to find the code where the rejection happens. The code that you highlight is meant to just support akka and pekko. The protocol suffix like `.tcp` or `.ssl.tcp` - we want to allow those but the lines you are highlighting are not the cause of the issue.
--
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-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [I] Seed nodes in a cluster using classic remoting [pekko]
Posted by "regiskuckaertz (via GitHub)" <gi...@apache.org>.
regiskuckaertz commented on issue #1854:
URL: https://github.com/apache/pekko/issues/1854#issuecomment-2906896001
💯 I was thinking the same, I'm disabling these checks entirely with a "noop" compat checker.
Thank you very much for the time you have spent investigating with me, this is much appreciated. Are you happy for me to close this issue?
--
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-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [I] Seed nodes in a cluster using classic remoting [pekko]
Posted by "regiskuckaertz (via GitHub)" <gi...@apache.org>.
regiskuckaertz commented on issue #1854:
URL: https://github.com/apache/pekko/issues/1854#issuecomment-2903538870
Given how many modules you need to publish, you may want to increase `sbt.repository.publish.attempts` from the default of 3.
https://github.com/sbt/librarymanagement/blob/a60161cd5ab7a4c5c278803d50b5b69eafadcdee/core/src/main/scala/sbt/internal/librarymanagement/LMSysProp.scala#L63-L64
Seen in the stack trace:
https://github.com/sbt/librarymanagement/blob/develop/ivy/src/main/scala/sbt/internal/librarymanagement/IvyActions.scala#L500-L504
--
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-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [I] Seed nodes in a cluster using classic remoting [pekko]
Posted by "regiskuckaertz (via GitHub)" <gi...@apache.org>.
regiskuckaertz commented on issue #1854:
URL: https://github.com/apache/pekko/issues/1854#issuecomment-2906871046
There is definitely logic that I can see, but it's currently used only when _sending_ the `InitJoin` message, to convert `pekko.*` into `akka.*`: https://github.com/apache/pekko/blob/9ab68569653dc40c794349da53060d11f324b2fa/cluster/src/main/scala/org/apache/pekko/cluster/SeedNodeProcess.scala#L84
Incidentally, ☝ is also the only place where the `enforce-on-join` flag is used.
So maybe the inverse could be added before doing the compat check: (1) check the enforce flag, (2) if flag is off then run the conversion logic from `akka.*` to `pekko.*`, (3) run the compat check and (4) if invalid and flag is off log a warning but send the `InitJoinAck` with a compatible config.
I will try adding a custom compat checker that returns `Valid`, to see if the remote akka node is happy with the config that comes back.
--
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-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [I] Seed nodes in a cluster using classic remoting [pekko]
Posted by "pjfanning (via GitHub)" <gi...@apache.org>.
pjfanning commented on issue #1854:
URL: https://github.com/apache/pekko/issues/1854#issuecomment-2906875460
@regiskuckaertz I've just been looking at the Pekko code and it does look like Pekko InitJoin checker will not be happy if the config it receives has akka configs instead of pekko configs. I think up until now, people trying this have just disabled the check.
The priority has been on fooling Akka nodes into accepting messages from Pekko nodes.
It may be feasible to adjust the Pekko JoinConfigCompatChecker to change the join config props from `akka` to `pekko` but one of the configs is `akka.version` and I don't know what to do about 'fixing' that property. We may still need to add extra logic that allows us to disable the version check but still do the other checks.
--
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-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org