Github user mxm commented on a diff in the pull request:
https://github.com/apache/flink/pull/2313#discussion_r75669289
--- Diff:
flink-runtime/src/main/java/org/apache/flink/runtime/client/JobClient.java ---
@@ -275,9 +275,35 @@ public static ClassLoader retrieveClassLoader(
public static JobExecutionResult awaitJobResult(JobListeningContext
listeningContext) throws JobExecutionException {
final JobID jobID = listeningContext.jobID;
+ final ActorRef jobClientActor = listeningContext.jobClientActor;
final Future<Object> jobSubmissionFuture =
listeningContext.jobResultFuture;
final ClassLoader classLoader = listeningContext.classLoader;
+ while (!jobSubmissionFuture.isCompleted()) {
+ try {
+ Thread.sleep(250);
--- End diff --
Actually, it's not quite as easy. If we simply wait on the ask timeout via
`Await.ready/result`, then we complete the `jobSubmissionFuture` with a timeout
(if the job runs longer then the timeout interval). Subsequent checks will
always return the same result.
Thus, we probably need something like a sleep here.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
