[ 
https://issues.apache.org/jira/browse/FLINK-19388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17201862#comment-17201862
 ] 

Dian Fu commented on FLINK-19388:
---------------------------------

I found the following exception in the log:
{code}
2020-09-24 03:13:06,860 ERROR 
org.apache.flink.runtime.rpc.akka.FencedAkkaRpcActor         [] - Error while 
executing remote procedure call public void 
org.apache.flink.runtime.jobmaster.JobMaster.notifyAllocationFailure(org.apache.flink.runtime.clusterframework.types.AllocationID,java.lang.Exception).
java.lang.reflect.InvocationTargetException: null
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
~[?:1.8.0_265]
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
~[?:1.8.0_265]
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 ~[?:1.8.0_265]
        at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_265]
        at 
org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleRpcInvocation(AkkaRpcActor.java:279)
 ~[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at 
org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleRpcMessage(AkkaRpcActor.java:199)
 ~[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at 
org.apache.flink.runtime.rpc.akka.FencedAkkaRpcActor.handleRpcMessage(FencedAkkaRpcActor.java:74)
 ~[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at 
org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleMessage(AkkaRpcActor.java:152)
 ~[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at akka.japi.pf.UnitCaseStatement.apply(CaseStatements.scala:26) 
[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at akka.japi.pf.UnitCaseStatement.apply(CaseStatements.scala:21) 
[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at scala.PartialFunction$class.applyOrElse(PartialFunction.scala:123) 
[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at akka.japi.pf.UnitCaseStatement.applyOrElse(CaseStatements.scala:21) 
[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:170) 
[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:171) 
[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:171) 
[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at akka.actor.Actor$class.aroundReceive(Actor.scala:517) 
[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at akka.actor.AbstractActor.aroundReceive(AbstractActor.scala:225) 
[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at akka.actor.ActorCell.receiveMessage(ActorCell.scala:592) 
[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at akka.actor.ActorCell.invoke(ActorCell.scala:561) 
[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:258) 
[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at akka.dispatch.Mailbox.run(Mailbox.scala:225) 
[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at akka.dispatch.Mailbox.exec(Mailbox.scala:235) 
[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at akka.dispatch.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260) 
[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at 
akka.dispatch.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339) 
[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at 
akka.dispatch.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979) 
[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at 
akka.dispatch.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107) 
[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
Caused by: java.util.ConcurrentModificationException
        at 
java.util.LinkedHashMap$LinkedHashIterator.nextNode(LinkedHashMap.java:719) 
~[?:1.8.0_265]
        at 
java.util.LinkedHashMap$LinkedKeyIterator.next(LinkedHashMap.java:742) 
~[?:1.8.0_265]
        at 
org.apache.flink.runtime.scheduler.SharedSlot.release(SharedSlot.java:218) 
~[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at 
org.apache.flink.runtime.jobmaster.slotpool.AllocatedSlot.releasePayload(AllocatedSlot.java:154)
 ~[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at 
org.apache.flink.runtime.jobmaster.slotpool.SlotPoolImpl.tryFailingAllocatedSlot(SlotPoolImpl.java:774)
 ~[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at 
org.apache.flink.runtime.jobmaster.slotpool.SlotPoolImpl.failAllocation(SlotPoolImpl.java:754)
 ~[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at 
org.apache.flink.runtime.jobmaster.JobMaster.internalFailAllocation(JobMaster.java:597)
 ~[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at 
org.apache.flink.runtime.jobmaster.JobMaster.notifyAllocationFailure(JobMaster.java:735)
 ~[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
{code}

> Streaming bucketing end-to-end test failed with "Number of running task 
> managers has not reached 4 within a timeout of 40 sec"
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-19388
>                 URL: https://issues.apache.org/jira/browse/FLINK-19388
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / FileSystem, Tests
>    Affects Versions: 1.12.0
>            Reporter: Dian Fu
>            Priority: Critical
>              Labels: test-stability
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=6876&view=logs&j=c88eea3b-64a0-564d-0031-9fdcd7b8abee&t=ff888d9b-cd34-53cc-d90f-3e446d355529
> {code}
> 2020-09-24T03:13:12.1370987Z Starting taskexecutor daemon on host fv-az661.
> 2020-09-24T03:13:12.1773280Z Number of running task managers 2 is not yet 4.
> 2020-09-24T03:13:16.4342638Z Number of running task managers 3 is not yet 4.
> 2020-09-24T03:13:20.4570976Z Number of running task managers 0 is not yet 4.
> 2020-09-24T03:13:24.4762428Z Number of running task managers 0 is not yet 4.
> 2020-09-24T03:13:28.4955622Z Number of running task managers 0 is not yet 4.
> 2020-09-24T03:13:32.5110079Z Number of running task managers 0 is not yet 4.
> 2020-09-24T03:13:36.5272551Z Number of running task managers 0 is not yet 4.
> 2020-09-24T03:13:40.5672343Z Number of running task managers 0 is not yet 4.
> 2020-09-24T03:13:44.5857760Z Number of running task managers 0 is not yet 4.
> 2020-09-24T03:13:48.6039181Z Number of running task managers 0 is not yet 4.
> 2020-09-24T03:13:52.6056222Z Number of running task managers has not reached 
> 4 within a timeout of 40 sec
> 2020-09-24T03:13:52.9275629Z Stopping taskexecutor daemon (pid: 13694) on 
> host fv-az661.
> 2020-09-24T03:13:53.1753734Z No standalonesession daemon (pid: 10610) is 
> running anymore on fv-az661.
> 2020-09-24T03:13:53.5812242Z Skipping taskexecutor daemon (pid: 10912), 
> because it is not running anymore on fv-az661.
> 2020-09-24T03:13:53.5813449Z Stopping taskexecutor daemon (pid: 11330) on 
> host fv-az661.
> 2020-09-24T03:13:53.5818053Z Stopping taskexecutor daemon (pid: 11632) on 
> host fv-az661.
> 2020-09-24T03:13:53.5819341Z Skipping taskexecutor daemon (pid: 11965), 
> because it is not running anymore on fv-az661.
> 2020-09-24T03:13:53.5820870Z Skipping taskexecutor daemon (pid: 12906), 
> because it is not running anymore on fv-az661.
> 2020-09-24T03:13:53.5821698Z Stopping taskexecutor daemon (pid: 13392) on 
> host fv-az661.
> 2020-09-24T03:13:53.5839544Z [FAIL] Test script contains errors.
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to