You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2018/07/24 12:15:00 UTC

[jira] [Commented] (FLINK-9937) Kubernetes(Minikube) Flink : cannot submit job in Flink UI with FLink 1.5.1

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

Chesnay Schepler commented on FLINK-9937:
-----------------------------------------

Is this the only exception in the JobManager logs? Could you run it again with DEBUG logging enabled?

The exception doesn't quite make sense considering the issue description.
According to the exception the UI attempted to retrieve information about a job.
This can only happen if the job was properly submitted, as otherwise no ID is returned.

> Kubernetes(Minikube) Flink : cannot submit job in Flink UI with FLink 1.5.1
> ---------------------------------------------------------------------------
>
>                 Key: FLINK-9937
>                 URL: https://issues.apache.org/jira/browse/FLINK-9937
>             Project: Flink
>          Issue Type: Wish
>            Reporter: Aleksandr Filichkin
>            Priority: Major
>
> Hi,
> I cannot submit Flink 1,5,1 job from UI on Kubernetes(minikube).
> But it works perfect with Flink 1.4.2
> I've created Flink artifacts like this:
> kubectl create -f jobmanager-deployment.yaml
> kubectl create -f taskmanager-deployment.yaml
> kubectl create -f jobmanager-service.yaml
> From https://ci.apache.org/projects/flink/flink-docs-release-1.2/setup/kubernetes.html
> Then make kubctl port-forward<JOBMANGER POD NAME> 8081
> Log:
>  2018-07-24 11:47:17,730 INFO  org.apache.flink.runtime.resourcemanager.slotmanager.SlotManager  - Registering TaskManager 407eac4f10f975b1334c89bd4896412b under 0a53ef353916bd20e7869e32d9419338 at the SlotManager.
> 2018-07-24 11:47:20,334 INFO  org.apache.flink.runtime.resourcemanager.slotmanager.SlotManager  - Registering TaskManager c750cbfadbf71b9de7fba2344760a758 under b9b04d04b79ee64996d6e5c2781b19d1 at the SlotManager.
> 2018-07-24 11:52:49,707 ERROR org.apache.flink.runtime.rest.handler.job.JobDetailsHandler   - Exception occurred in REST handler.
> org.apache.flink.runtime.rest.NotFoundException: Job 6bc30e7df8f3410c110150fc0c90ce69 not found
> 	at org.apache.flink.runtime.rest.handler.job.AbstractExecutionGraphHandler.lambda$handleRequest$1(AbstractExecutionGraphHandler.java:90)
> 	at java.util.concurrent.CompletableFuture.uniExceptionally(CompletableFuture.java:870)
> 	at java.util.concurrent.CompletableFuture$UniExceptionally.tryFire(CompletableFuture.java:852)
> 	at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
> 	at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1977)
> 	at org.apache.flink.runtime.rest.handler.legacy.ExecutionGraphCache.lambda$getExecutionGraph$0(ExecutionGraphCache.java:133)
> 	at java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:760)
> 	at java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:736)
> 	at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
> 	at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1977)
> 	at org.apache.flink.runtime.concurrent.FutureUtils$1.onComplete(FutureUtils.java:811)
> 	at akka.dispatch.OnComplete.internal(Future.scala:258)
> 	at akka.dispatch.OnComplete.internal(Future.scala:256)
> 	at akka.dispatch.japi$CallbackBridge.apply(Future.scala:186)
> 	at akka.dispatch.japi$CallbackBridge.apply(Future.scala:183)
> 	at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:36) 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)