AtScale engine error - actor name [healthActorSupervisor] is not unique!
Hi
Company that I work for is considering using AtScale to process large datasets (milions of rows) with AtScale.
I was tasked with evaluation feasibility of EKS execution.
Running in EKS cluster : https://documentation.atscale.com/container/installation-guides/kubernetes/installing-atscale
Everything spins up except the Engine, that gives an error which does not indicate any configuration/infrastructure issues :
"atscale engine actor name [healthActorSupervisor] is not unique! "
Trace :
│ org.apache.pekko.actor.InvalidActorNameException: actor name [healthActorSupervisor] is not unique!
│ at org.apache.pekko.actor.dungeon.ChildrenContainer$NormalChildrenContainer.reserve(ChildrenContainer.scala:144) │ at org.apache.pekko.actor.dungeon.Children.reserveChild(Children.scala:156) │
at org.apache.pekko.actor.dungeon.Children.reserveChild$(Children.scala:154)
│ at org.apache.pekko.actor.ActorCell.reserveChild(ActorCell.scala:420)
│ at org.apache.pekko.actor.dungeon.Children.makeChild(Children.scala:308)
│ at org.apache.pekko.actor.dungeon.Children.attachChild(Children.scala:62)
│ at org.apache.pekko.actor.dungeon.Children.attachChild$(Children.scala:61)
│ at org.apache.pekko.actor.ActorCell.attachChild(ActorCell.scala:420) │
at org.apache.pekko.actor.ActorSystemImpl.actorOf(ActorSystem.scala:909)
│ at com.atscale.engine.actors.ActorFactory.localActor(ActorFactory.scala:21)
│ at com.atscale.engine.actors.ActorFactory.localActor$(ActorFactory.scala:20)
│ at com.atscale.engine.actors.ActorFactory$.localActor(ActorFactory.scala:45) │
at com.atscale.engine.actors.RouteDefinitions.healthActor(routes.scala:138)
│ at com.atscale.engine.actors.CommonRoutes.<init>(routes.scala:110)
│ at com.atscale.engine.configuration.MainProfile$MainRoutes.<init>(MainProfile.scala:47) │
at com.atscale.engine.configuration.MainProfile.routes$lzycompute(MainProfile.scala:44)
│ at com.atscale.engine.configuration.MainProfile.routes(MainProfile.scala:43)
│ at com.atscale.engine.actors.package$.routes$lzycompute(package.scala:62)
│ at com.atscale.engine.actors.package$.routes(package.scala:62)
│ at com.atscale.engine.core.schema.SchemaManager$.futureSchemas(SchemaManager.scala:583)
│ at com.atscale.engine.core.schema.SchemaManager$.allSchemas(SchemaManager.scala:682) com.atscale.engine.aggregation.PreferredStoreRowCounter$.allProjectsAndPreferredStores(PreferredStoreRowCounter.scala:270) com.atscale.engine.aggregation.PreferredStoreRowCounter.$anonfun$initializeRowCountMap$8(PreferredStoreRowCounter.scala:145) at scala.concurrent.impl.Promise$Transformation.run(Promise.scala:470)
│ at org.apache.pekko.dispatch.BatchingExecutor$AbstractBatch.processBatch(BatchingExecutor.scala:73)
│ at org.apache.pekko.dispatch.BatchingExecutor$BlockableBatch.$anonfun$run$1(BatchingExecutor.scala:110)
│ at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.scala:18)
│ at scala.concurrent.BlockContext$.withBlockContext(BlockContext.scala:94)
│ at org.apache.pekko.dispatch.BatchingExecutor$BlockableBatch.run(BatchingExecutor.scala:110)
│ at org.apache.pekko.dispatch.TaskInvocation.run(AbstractDispatcher.scala:59) kamon.instrumentation.executor.ExecutorInstrumentation$InstrumentedForkJoinPool$TimingRunnable.run(ExecutorInstrumentation.scala:698)
│ at org.apache.pekko.dispatch.ForkJoinExecutorConfigurator$PekkoForkJoinTask.exec(ForkJoinExecutorConfigurator.scala:57)
│ at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:387)
│ at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1312)
│ at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1843)
│ at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1808) │
at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:188)
Could anyone please give us a hint what could be the cause of this error ?
Regards
Comments
1 comment
Are you doing any kind of HA for your deploy? I have not done anything with multi-engines or replicas but if you are trying to deploy it could be an issue with the default engine naming convention or something along those lines...what version are you trying to deploy? I just got 2024.8.0 running locally this week but its a single engine deployment (and not in EKS)
Please sign in to leave a comment.