Re: beam + flink + k8

2023-02-02 Thread P Singh
n Job to flink > it's not showing or flink UI or simply hangs without any error. > > > > Sent from my Galaxy > > > Original message > From: Jan Lukavský > Date: 02/02/2023 15:07 (GMT+05:30) > To: user@flink.apache.org > Subject: Re: beam +

Re: beam + flink + k8

2023-02-02 Thread Jan Lukavský
ubmit python Job to flink it's not showing or flink UI or simply hangs without any error. Sent from my Galaxy Original message From: Jan Lukavský Date: 02/02/2023 15:07 (GMT+05:30) To: user@flink.apache.org Subject: Re: beam + flink + k8 I'm not sure how exactly minik

Re: beam + flink + k8

2023-02-02 Thread bigdatadeveloper8
bject: Re: beam + flink + k8 I'm not sure how exactly minikube exposes the jobmanager, but in GKE you likely need to port-forward it, e.g.  $ kubectl port-forward svc/flink-jobmanager 8081:8081 This should make jobmanager accessible via localhost:8081. For

Re: beam + flink + k8

2023-02-02 Thread Jan Lukavský
I'm not sure how exactly minikube exposes the jobmanager, but in GKE you likely need to port-forward it, e.g.  $ kubectl port-forward svc/flink-jobmanager 8081:8081 This should make jobmanager accessible via localhost:8081. For production cases you might want to use a different approach, like

Re: beam + flink + k8

2023-02-01 Thread P Singh
Hi Jan, Thanks for the reply, I was able to submit the job to flink but it's failing due to an OOM issue so I am moving to the GKE. I got the flink UI there but submitted a job not appearing on flink UI. I am using the same script which I shared with you.. Do I need to make some changes for Google

Re: beam + flink + k8

2023-01-31 Thread Jan Lukavský
The script looks good to me, did you run the SDK harness? External environment needs the SDK harness to be run externally, see [1]. Generally, the best option is DOCKER, but that usually does not work in k8s. For this, you might try PROCESS environment and build your own docker image for flink,

Re: beam + flink + k8

2023-01-31 Thread Jan Lukavský
Hi, can you please share the also the script itself? I'd say that the problem is that the flink jobmanager is not accessible through localhost:8081, because it runs inside the minikube. You need to expose it outside of the minikube via [1], or run the script from pod inside the minikube and a

Re: beam + flink + k8

2023-01-30 Thread Jan Lukavský
Hi, can you please share the command-line and complete output of the script? Are you using minikube? Can you share list of your running pods?  Jan On 1/30/23 14:25, P Singh wrote: Hi Team, I am trying to run beam job on top of flink on my local machine (kubernetes).  I have flink 1.14 an

beam + flink + k8

2023-01-30 Thread P Singh
Hi Team, I am trying to run beam job on top of flink on my local machine (kubernetes). I have flink 1.14 and beam 2.43 images both running but when i submit the job it's not reaching to the flink cluster and getting failed with below error. ERROR:apache_beam.utils.subprocess_server:Starting job