[
https://issues.apache.org/jira/browse/FLINK-9056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16430562#comment-16430562
]
ASF GitHub Bot commented on FLINK-9056:
---------------------------------------
GitHub user yuqi1129 opened a pull request:
https://github.com/apache/flink/pull/5829
[FLINK-9056] [jobmanager] Job submission fails with AskTimeoutExcepti…
## What is the purpose of the change
This pull request makes the jobmanager return specific information if there
is not enough sloth available when flink dataset job request for resources.
Now, flink only return AskTimeoutException cause by timeout.
## Brief change log
- *job retrieve the TaskInfo from the blob cache*
## Verifying this change
*(Please pick either of the following options)*
This change is a trivial rework / code cleanup without any test coverage.
*(or)*
This change is already covered by existing tests, such as *(please describe
tests)*.
*(or)*
This change added tests and can be verified as follows:
*(example:)*
- *Added integration tests for end-to-end deployment with large payloads
(100MB)*
- *Extended integration test for recovery after master (JobManager)
failure*
- *Added test that validates that TaskInfo is transferred only once
across recoveries*
- *Manually verified the change by running a 4 node cluser with 2
JobManagers and 4 TaskManagers, a stateful streaming program, and killing one
JobManager and two TaskManagers during the execution, verifying that recovery
happens correctly.*
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): (yes / no)
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: (yes / no)
- The serializers: (yes / no / don't know)
- The runtime per-record code paths (performance sensitive): (yes / no /
don't know)
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
- The S3 file system connector: (yes / no / don't know)
## Documentation
- Does this pull request introduce a new feature? (yes / no)
- If yes, how is the feature documented? (not applicable / docs /
JavaDocs / not documented)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/yuqi1129/flink TimeOutProblem
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/5829.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5829
----
commit 60738d19aa4ed13a29141a5d446074203d815809
Author: hzyuqi1 <hzyuqi1@...>
Date: 2018-04-09T13:39:17Z
[FLINK-9056] [jobmanager] Job submission fails with AskTimeoutException if
not enough slots are available
----
> Job submission fails with AskTimeoutException if not enough slots are
> available
> -------------------------------------------------------------------------------
>
> Key: FLINK-9056
> URL: https://issues.apache.org/jira/browse/FLINK-9056
> Project: Flink
> Issue Type: Improvement
> Components: Job-Submission
> Affects Versions: 1.5.0
> Environment: * FLIP-6 enabled
> * Local Flink instance with fixed number of TMs
> * Job parallelism exceeds available slots
> Reporter: Fabian Hueske
> Assignee: yuqi
> Priority: Major
>
> The error message if a job submission fails due to lack of available slots is
> not helpful:
> {code:java}
> Caused by: akka.pattern.AskTimeoutException: Ask timed out on
> [Actor[akka://flink/user/8f0fabba-4021-45b6-a1f7-b8afd6627640#-574617182|#-574617182]]
> after [300000 ms]. Sender[null] sent message of type
> "org.apache.flink.runtime.rpc.messages.LocalRpcInvocation".
> at
> akka.pattern.PromiseActorRef$$anonfun$1.apply$mcV$sp(AskSupport.scala:604)
> at akka.actor.Scheduler$$anon$4.run(Scheduler.scala:126)
> at
> scala.concurrent.Future$InternalCallbackExecutor$.unbatchedExecute(Future.scala:601)
> at
> scala.concurrent.BatchingExecutor$class.execute(BatchingExecutor.scala:109)
> at
> scala.concurrent.Future$InternalCallbackExecutor$.execute(Future.scala:599)
> at
> akka.actor.LightArrayRevolverScheduler$TaskHolder.executeTask(LightArrayRevolverScheduler.scala:329)
> at
> akka.actor.LightArrayRevolverScheduler$$anon$4.executeBucket$1(LightArrayRevolverScheduler.scala:280)
> at
> akka.actor.LightArrayRevolverScheduler$$anon$4.nextTick(LightArrayRevolverScheduler.scala:284)
> at
> akka.actor.LightArrayRevolverScheduler$$anon$4.run(LightArrayRevolverScheduler.scala:236)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
