You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@pekko.apache.org by "iosyyy (via GitHub)" <gi...@apache.org> on 2025/09/15 07:37:57 UTC
[D] Migration from Akka to Pekko [pekko]
GitHub user iosyyy created a discussion: Migration from Akka to Pekko
Cluster Bootstrap uses hostname with hyphens instead of IP (uses `10-121-129-17.default.pod.cluster.local` instead of `10.121.129.17`)
GitHub link: https://github.com/apache/pekko/discussions/2221
----
This is an automatically sent email for notifications@pekko.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@pekko.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [D] Migration from Akka to Pekko [pekko]
Posted by "pjfanning (via GitHub)" <gi...@apache.org>.
GitHub user pjfanning added a comment to the discussion: Migration from Akka to Pekko
@iosyyy can you give a more detailed description?
GitHub link: https://github.com/apache/pekko/discussions/2221#discussioncomment-14400950
----
This is an automatically sent email for notifications@pekko.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@pekko.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [D] Migration from Akka to Pekko [pekko]
Posted by "iosyyy (via GitHub)" <gi...@apache.org>.
GitHub user iosyyy added a comment to the discussion: Migration from Akka to Pekko
My conf:
```
pekko {
actor {
serializers {
jackson-json = "org.apache.pekko.serialization.jackson.JacksonJsonSerializer"
}
serialization-bindings {
"ai.saharalabs.model.IShardMessage" = jackson-json
"ai.saharalabs.model.TraceableMessage" = jackson-json
}
}
coordinated-shutdown {
exit-jvm = on
}
cluster {
shutdown-after-unsuccessful-join-seed-nodes = 600s
seed-nodes = []
}
actor.blocking-io-dispatcher.thread-pool-executor.fixed-pool-size = 16
remote.artery {
canonical {
hostname = "<getHostAddress>"
}
}
discovery {
kubernetes-api {
pod-label-selector = "actor-system-name=%s"
use-pod-ip = on
prefer-ip-addresses = true
}
}
management {
http {
bind-hostname = "0.0.0.0"
port = 7626
}
cluster.bootstrap {
new-cluster-enabled = on
contact-point-discovery {
port-name = "management"
discovery-method = kubernetes-api
required-contact-point-nr = ${?REQUIRED_CONTACT_POINT_NR}
stable-margin = 5s
}
}
}
}
```
GitHub link: https://github.com/apache/pekko/discussions/2221#discussioncomment-14401024
----
This is an automatically sent email for notifications@pekko.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@pekko.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [D] Migration from Akka to Pekko [pekko]
Posted by "pjfanning (via GitHub)" <gi...@apache.org>.
GitHub user pjfanning added a comment to the discussion: Migration from Akka to Pekko
What version of Pekko? What version of Akka?
Pekko is a copy of Akka (from before they changed their license). If you use a newer version of Akka from after the license change then they might have extra changes that Pekko doesn't have. Pekko hasn't changed the cluster code much.
Are you using Pekko 1.1+?. One change in Pekko 1.1+ is that we upgraded to Netty 4 but Netty is not the default transport, Artery/Aeron is (and we haven't made big changes there).
GitHub link: https://github.com/apache/pekko/discussions/2221#discussioncomment-14401096
----
This is an automatically sent email for notifications@pekko.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@pekko.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [D] Migration from Akka to Pekko [pekko]
Posted by "iosyyy (via GitHub)" <gi...@apache.org>.
GitHub user iosyyy added a comment to the discussion: Migration from Akka to Pekko
When Pekko Cluster Bootstrap uses Kubernetes Discovery, it queries the Kubernetes API for endpoints (pods), and by default it resolves to the hostname of the pod. Kubernetes returns DNS-style names rather than raw IP addresses. However, this worked fine on Akka but not on Pekko.
Observed Error
```
Probing [http://10-121-129-19.default.pod.cluster.local:7626/bootstrap/seed-nodes] failed due to: Probing timeout of [http://10-121-129-19.default.pod.cluster.local:7626]
```
GitHub link: https://github.com/apache/pekko/discussions/2221#discussioncomment-14401017
----
This is an automatically sent email for notifications@pekko.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@pekko.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [D] Migration from Akka to Pekko [pekko]
Posted by "He-Pin (via GitHub)" <gi...@apache.org>.
GitHub user He-Pin added a comment to the discussion: Migration from Akka to Pekko
He needs to retrieve the IP address from Kubernetes. Maybe use Pekko management.
GitHub link: https://github.com/apache/pekko/discussions/2221#discussioncomment-14401255
----
This is an automatically sent email for notifications@pekko.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@pekko.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [D] Migration from Akka to Pekko [pekko]
Posted by "iosyyy (via GitHub)" <gi...@apache.org>.
GitHub user iosyyy deleted a comment on the discussion: Migration from Akka to Pekko
When Pekko Cluster Bootstrap uses Kubernetes Discovery, it queries the Kubernetes API for endpoints (pods), and by default it resolves to the hostname of the pod. Kubernetes returns DNS-style names rather than raw IP addresses. However, this worked fine on Akka but not on Pekko.
Observed Error
```
Probing [http://10-121-129-19.default.pod.cluster.local:7626/bootstrap/seed-nodes] failed due to: Probing timeout of [http://10-121-129-19.default.pod.cluster.local:7626]
```
GitHub link: https://github.com/apache/pekko/discussions/2221#discussioncomment-14401018
----
This is an automatically sent email for notifications@pekko.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@pekko.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [D] Migration from Akka to Pekko [pekko]
Posted by "iosyyy (via GitHub)" <gi...@apache.org>.
GitHub user iosyyy deleted a comment on the discussion: Migration from Akka to Pekko
My conf:
```
pekko {
actor {
serializers {
jackson-json = "org.apache.pekko.serialization.jackson.JacksonJsonSerializer"
}
serialization-bindings {
"ai.saharalabs.model.IShardMessage" = jackson-json
"ai.saharalabs.model.TraceableMessage" = jackson-json
}
}
coordinated-shutdown {
exit-jvm = on
}
cluster {
shutdown-after-unsuccessful-join-seed-nodes = 600s
seed-nodes = []
}
actor.blocking-io-dispatcher.thread-pool-executor.fixed-pool-size = 16
remote.artery {
canonical {
hostname = "<getHostAddress>"
}
}
discovery {
kubernetes-api {
pod-label-selector = "actor-system-name=%s"
use-pod-ip = on
prefer-ip-addresses = true
}
}
management {
http {
bind-hostname = "0.0.0.0"
port = 7626
}
cluster.bootstrap {
new-cluster-enabled = on
contact-point-discovery {
port-name = "management"
discovery-method = kubernetes-api
required-contact-point-nr = ${?REQUIRED_CONTACT_POINT_NR}
stable-margin = 5s
}
}
}
}
```
GitHub link: https://github.com/apache/pekko/discussions/2221#discussioncomment-14401024
----
This is an automatically sent email for notifications@pekko.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@pekko.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [D] Migration from Akka to Pekko [pekko]
Posted by "iosyyy (via GitHub)" <gi...@apache.org>.
GitHub user iosyyy added a comment to the discussion: Migration from Akka to Pekko
When Pekko Cluster Bootstrap uses Kubernetes Discovery, it queries the Kubernetes API for endpoints (pods), and by default it resolves to the hostname of the pod. Kubernetes returns DNS-style names rather than raw IP addresses. However, this worked fine on Akka but not on Pekko.
Observed Error
```
Probing [http://10-121-129-19.default.pod.cluster.local:7626/bootstrap/seed-nodes] failed due to: Probing timeout of [http://10-121-129-19.default.pod.cluster.local:7626]
```
GitHub link: https://github.com/apache/pekko/discussions/2221#discussioncomment-14401018
----
This is an automatically sent email for notifications@pekko.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@pekko.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org