Akka to Pekko Migration for Deploy

Akka is a toolkit for building highly concurrent, distributed, and resilient message-driven applications for Java and Scala. Apache Pekko is a fork of Akka 2.6.x, created prior to the Akka project's adoption of the Business Source License.

Starting with version 24.1, Digital.ai Deploy has migrated from Akka to Apache Pekko.

note

When setting up Deploy in cluster mode, any occurrences of akka in the following configuration files will cause startup to fail:

• XL_DEPLOY_SERVER_HOME/centralConfiguration/deploy-cluster.yaml
• XL_DEPLOY_SERVER_HOME/centralConfiguration/deploy-jmx.yaml
• XL_DEPLOY_SERVER_HOME/centralConfiguration/deploy-server.yaml
• XL_DEPLOY_SERVER_HOME/centralConfiguration/deploy-task.yaml

To resolve this, replace all Akka references with their Pekko equivalents. This includes packages, class names, jar names, and URLs. For detailed migration instructions, see the Pekko Migration Guide.

important

While Deploy 24.1+ includes the correct Pekko configurations by default, upgrades from earlier versions require manual updates from akka to pekko.

If any configuration file contains Akka references during an upgrade, you'll see the error: "Configuration settings found which contains not supported term: akka. See the migration guide for details about fixing your configuration"

Configuration Examples

Before (Akka Configuration)

deploy-cluster.yaml

actor:
    loggers:
        - "akka.event.slf4j.Slf4jLogger"
    loglevel: "INFO"
    provider: "akka.cluster.ClusterActorRefProvider"

deploy-jmx.yaml

kamon:
    show-aspectj-missing-warning: yes
    metric:
        track-unmatched-entities: yes
    filters:
        akka-dispatcher:
            includes:
                - "PlannerActorSystem/**"
                - "task-sys/**"
                - "xl-scheduler-system/**"
            excludes: []

deploy-server.yaml

akka:
    io:
        dns:
            resolver: async-dns
    loglevel: INFO

deploy-task.yaml

system:
    akka:
        loggers:
            - "akka.event.slf4j.Slf4jLogger"
            - "akka.event.Logging$DefaultLogger"
        loglevel: "INFO"

After (Pekko Configuration)

deploy-cluster.yaml

pekko:
    actor:
        loggers:
            - "org.apache.pekko.event.slf4j.Slf4jLogger"
        loglevel: INFO
        provider: "org.apache.pekko.cluster.ClusterActorRefProvider"

deploy-jmx.yaml

kamon:
    show-aspectj-missing-warning: yes
    metric:
        track-unmatched-entities: yes
    filters:
        pekko-dispatcher:
            includes:
                - "PlannerActorSystem/**"
                - "task-sys/**"
                - "xl-scheduler-system/**"
            excludes: []

deploy-server.yaml

pekko:
    io:
        dns:
            resolver: async-dns
    loglevel: INFO

deploy-task.yaml

system:
    pekko:
        loggers:
            - "org.apache.pekko.event.slf4j.Slf4jLogger"
            - "org.apache.pekko.event.Logging$DefaultLogger"
        loglevel: "INFO"

Common Configuration Mappings

Akka	Pekko
akka	pekko
"akka.event.slf4j.Slf4jLogger"	"org.apache.pekko.event.slf4j.Slf4jLogger"
"akka.event.slf4j.Slf4jLoggingFilter"	"org.apache.pekko.event.slf4j.Slf4jLoggingFilter"
"com.typesafe.akka.extension.quartz.QuartzSchedulerExtension"	"org.apache.pekko.extension.quartz.QuartzSchedulerExtension"
"io.altoo.akka.serialization.kryo.KryoSerializer"	"io.altoo.serialization.kryo.pekko.PekkoKryoSerializer"
"akka.actor.ActorRef"	"org.apache.pekko.actor.ActorRef"
akka-persistence	pekko-persistence
akka-persistence-jdbc	pekko-persistence-jdbc
"akka.persistence.jdbc.journal.dao.legacy.ByteArrayJournalDao"	"org.apache.pekko.persistence.jdbc.journal.dao.legacy.ByteArrayJournalDao"
"akka.persistence.jdbc.snapshot.dao.legacy.ByteArraySnapshotDao"	"org.apache.pekko.persistence.jdbc.snapshot.dao.legacy.ByteArraySnapshotDao"
akka-kryo-serialization	pekko-kryo-serialization
"akka.cluster.pubsub.DistributedPubSub"	"org.apache.pekko.cluster.pubsub.DistributedPubSub"
"akka.cluster.ClusterActorRefProvider"	"org.apache.pekko.cluster.ClusterActorRefProvider"

If you have custom plugins, verify that all Akka configurations are updated to their Pekko equivalents.

important

For assistance with Pekko configuration mappings, contact Customer Support.