最新消息:雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客

Flink CDC Task Frequently Failing - has no more allocated slots for job - Stack Overflow

programmeradmin3浏览0评论

I'm running a Flink CDC job (version 3.0.0) that synchronizes data from MySQL 8.0.35 to Apache Doris, but it keeps failing with the error Could not allocate the required slot within timeout. Has no more allocated slots for job.

configurations: taskmanager.numberOfTaskSlots: 4

linux resources is ok

errors:

2025-04-02 12:46:32 .apache.flink.util.FlinkExpectedException: TaskExecutor pekko.tcp://[email protected]:13795/user/rpc/taskmanager_0 has no more allocated slots for job 4478629ba4325491e27d87c98fcdd49c. at .apache.flink.runtime.taskexecutor.TaskExecutor.closeJobManagerConnectionIfNoAllocatedResources(TaskExecutor.java:2056) at .apache.flink.runtime.taskexecutor.TaskExecutor.freeSlotInternal(TaskExecutor.java:2032) at .apache.flink.runtime.taskexecutor.TaskExecutor.timeoutSlot(TaskExecutor.java:2070) at .apache.flink.runtime.taskexecutor.TaskExecutor.access$3600(TaskExecutor.java:188) at .apache.flink.runtime.taskexecutor.TaskExecutor$SlotActionsImpl.lambda$timeoutSlot$1(TaskExecutor.java:2514) at .apache.flink.runtime.rpc.pekko.PekkoRpcActor.lambda$handleRunAsync$4(PekkoRpcActor.java:451) at .apache.flink.runtime.concurrent.ClassLoadingUtils.runWithContextClassLoader(ClassLoadingUtils.java:68) at .apache.flink.runtime.rpc.pekko.PekkoRpcActor.handleRunAsync(PekkoRpcActor.java:451) at .apache.flink.runtime.rpc.pekko.PekkoRpcActor.handleRpcMessage(PekkoRpcActor.java:218) at .apache.flink.runtime.rpc.pekko.PekkoRpcActor.handleMessage(PekkoRpcActor.java:168) at .apache.pekko.japi.pf.UnitCaseStatement.apply(CaseStatements.scala:33) at .apache.pekko.japi.pf.UnitCaseStatement.apply(CaseStatements.scala:29) at scala.PartialFunction.applyOrElse(PartialFunction.scala:127) at scala.PartialFunction.applyOrElse$(PartialFunction.scala:126) at .apache.pekko.japi.pf.UnitCaseStatement.applyOrElse(CaseStatements.scala:29) at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:175) at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:176) at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:176) at .apache.pekko.actor.Actor.aroundReceive(Actor.scala:547) at .apache.pekko.actor.Actor.aroundReceive$(Actor.scala:545) at .apache.pekko.actor.AbstractActor.aroundReceive(AbstractActor.scala:229) at .apache.pekko.actor.ActorCell.receiveMessage(ActorCell.scala:590) at .apache.pekko.actor.ActorCell.invoke(ActorCell.scala:557) at .apache.pekko.dispatch.Mailbox.processMailbox(Mailbox.scala:280) at .apache.pekko.dispatch.Mailbox.run(Mailbox.scala:241) at .apache.pekko.dispatch.Mailbox.exec(Mailbox.scala:253) at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289) at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1067) at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1703) at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:172)

can someone help find out why

I'm running a Flink CDC job (version 3.0.0) that synchronizes data from MySQL 8.0.35 to Apache Doris, but it keeps failing with the error Could not allocate the required slot within timeout. Has no more allocated slots for job.

configurations: taskmanager.numberOfTaskSlots: 4

linux resources is ok

errors:

2025-04-02 12:46:32 .apache.flink.util.FlinkExpectedException: TaskExecutor pekko.tcp://[email protected]:13795/user/rpc/taskmanager_0 has no more allocated slots for job 4478629ba4325491e27d87c98fcdd49c. at .apache.flink.runtime.taskexecutor.TaskExecutor.closeJobManagerConnectionIfNoAllocatedResources(TaskExecutor.java:2056) at .apache.flink.runtime.taskexecutor.TaskExecutor.freeSlotInternal(TaskExecutor.java:2032) at .apache.flink.runtime.taskexecutor.TaskExecutor.timeoutSlot(TaskExecutor.java:2070) at .apache.flink.runtime.taskexecutor.TaskExecutor.access$3600(TaskExecutor.java:188) at .apache.flink.runtime.taskexecutor.TaskExecutor$SlotActionsImpl.lambda$timeoutSlot$1(TaskExecutor.java:2514) at .apache.flink.runtime.rpc.pekko.PekkoRpcActor.lambda$handleRunAsync$4(PekkoRpcActor.java:451) at .apache.flink.runtime.concurrent.ClassLoadingUtils.runWithContextClassLoader(ClassLoadingUtils.java:68) at .apache.flink.runtime.rpc.pekko.PekkoRpcActor.handleRunAsync(PekkoRpcActor.java:451) at .apache.flink.runtime.rpc.pekko.PekkoRpcActor.handleRpcMessage(PekkoRpcActor.java:218) at .apache.flink.runtime.rpc.pekko.PekkoRpcActor.handleMessage(PekkoRpcActor.java:168) at .apache.pekko.japi.pf.UnitCaseStatement.apply(CaseStatements.scala:33) at .apache.pekko.japi.pf.UnitCaseStatement.apply(CaseStatements.scala:29) at scala.PartialFunction.applyOrElse(PartialFunction.scala:127) at scala.PartialFunction.applyOrElse$(PartialFunction.scala:126) at .apache.pekko.japi.pf.UnitCaseStatement.applyOrElse(CaseStatements.scala:29) at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:175) at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:176) at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:176) at .apache.pekko.actor.Actor.aroundReceive(Actor.scala:547) at .apache.pekko.actor.Actor.aroundReceive$(Actor.scala:545) at .apache.pekko.actor.AbstractActor.aroundReceive(AbstractActor.scala:229) at .apache.pekko.actor.ActorCell.receiveMessage(ActorCell.scala:590) at .apache.pekko.actor.ActorCell.invoke(ActorCell.scala:557) at .apache.pekko.dispatch.Mailbox.processMailbox(Mailbox.scala:280) at .apache.pekko.dispatch.Mailbox.run(Mailbox.scala:241) at .apache.pekko.dispatch.Mailbox.exec(Mailbox.scala:253) at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289) at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1067) at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1703) at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:172)

can someone help find out why

Share Improve this question asked Apr 2 at 8:32 user23927448user23927448 1 New contributor user23927448 is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.
Add a comment  | 

1 Answer 1

Reset to default 0

It is estimated that the slot should be increased, or the concurrency of flink itself should be lowered.

发布评论

评论列表(0)

  1. 暂无评论