Fwd: Not able to run with two task manager in native flink in kubernetes with high availability mode

[Priyanka Manickam]

---------- Forwarded message ---------
From: Priyanka Manickam <[hidden email]>
Date: Fri, 9 Apr 2021, 23:03
Subject: Fwd: Not able to run with two task manager in native flink in kubernetes with high availability mode
To: <[hidden email]>

---------- Forwarded message ---------
From: Priyanka Manickam <[hidden email]>
Date: Fri, 9 Apr 2021, 18:56
Subject: Not able to run with two task manager in native flink in kubernetes with high availability mode
To: <[hidden email]>

Hi all,

I am using flink deployment in azure kubernetes . The mode i have chosen is native deployment high availabilty depolyment in kubernetes.

But when i used the below configuration. I am seeing only one task manager is running.but i need to run two taskmanger. I have searched the configuration for it in flink website, but did not find any solution for this. Also used kubernetes.taskmanager.node-selector=1, then pod only i am not able to see..

Could some one help with the commands to run two taskmanger in native flink in kubernetes with high availability mode.

Please find the Attached configuration used and kindly guide with the solution for it.

Thanks, 

Priyanka Manickam

[Yang Wang]

Hi Priyanka Manickam,

If you are using the native Kubernetes integration, the TaskManagers will be started/stopped dynamically on demands.

It also means you could not control the number of running TaskManager pods. Refer to here[1] for more information.

In your case, numOfTaskSlots has been configured to 25 and the default parallelism is 8, so the second TaskManager

is unnecessary. If you want to running your Flink application with two TaskManagers, please set the "taskmanager.numberOfTaskSlots"

to 4 and keep the parallelism to 8. Then you could find two started TaskManagers and without spare slots.

Please note that "kubernetes.taskmanager.node-selector" is used to start TaskManager pods on specific nodes. It

is not used to configure the number of TaskManagers. Refer to K8s documentation for more information[2].

[1]. https://flink.apache.org/2021/02/10/native-k8s-with-ha.html

[2]. https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/

Best,

Yang

Priyanka Manickam <[hidden email]> 于2021年4月10日周六 下午3:47写道：

---------- Forwarded message ---------
From: Priyanka Manickam <[hidden email]>
Date: Fri, 9 Apr 2021, 23:03
Subject: Fwd: Not able to run with two task manager in native flink in kubernetes with high availability mode
To: <[hidden email]>

---------- Forwarded message ---------
From: Priyanka Manickam <[hidden email]>
Date: Fri, 9 Apr 2021, 18:56
Subject: Not able to run with two task manager in native flink in kubernetes with high availability mode
To: <[hidden email]>

Hi all,

I am using flink deployment in azure kubernetes . The mode i have chosen is native deployment high availabilty depolyment in kubernetes.

But when i used the below configuration. I am seeing only one task manager is running.but i need to run two taskmanger. I have searched the configuration for it in flink website, but did not find any solution for this. Also used kubernetes.taskmanager.node-selector=1, then pod only i am not able to see..

Could some one help with the commands to run two taskmanger in native flink in kubernetes with high availability mode.

Please find the Attached configuration used and kindly guide with the solution for it.

Thanks, 

Priyanka Manickam

[Priyanka Manickam]

Good Day Yang

Thanks for your early response.

I do have tried the configuration mentioned in the previous reply with parallelism 8 and -Dtaskmanager.numberOfTaskSlots=4.

But still seeing only one task manager is running in azure kubernetes.

Could you please check this one and guide us if any configuration i have missed out or to be added.

Thanks,

Priyanka Manickam

On Mon, 12 Apr 2021, 12:05 Yang Wang, <[hidden email]> wrote:

Hi Priyanka Manickam,

If you are using the native Kubernetes integration, the TaskManagers will be started/stopped dynamically on demands.

It also means you could not control the number of running TaskManager pods. Refer to here[1] for more information.

In your case, numOfTaskSlots has been configured to 25 and the default parallelism is 8, so the second TaskManager

is unnecessary. If you want to running your Flink application with two TaskManagers, please set the "taskmanager.numberOfTaskSlots"

to 4 and keep the parallelism to 8. Then you could find two started TaskManagers and without spare slots.

Please note that "kubernetes.taskmanager.node-selector" is used to start TaskManager pods on specific nodes. It

is not used to configure the number of TaskManagers. Refer to K8s documentation for more information[2].

[1]. https://flink.apache.org/2021/02/10/native-k8s-with-ha.html

[2]. https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/

Best,

Yang

Priyanka Manickam <[hidden email]> 于2021年4月10日周六 下午3:47写道：

---------- Forwarded message ---------
From: Priyanka Manickam <[hidden email]>
Date: Fri, 9 Apr 2021, 23:03
Subject: Fwd: Not able to run with two task manager in native flink in kubernetes with high availability mode
To: <[hidden email]>

---------- Forwarded message ---------
From: Priyanka Manickam <[hidden email]>
Date: Fri, 9 Apr 2021, 18:56
Subject: Not able to run with two task manager in native flink in kubernetes with high availability mode
To: <[hidden email]>

Hi all,

I am using flink deployment in azure kubernetes . The mode i have chosen is native deployment high availabilty depolyment in kubernetes.

But when i used the below configuration. I am seeing only one task manager is running.but i need to run two taskmanger. I have searched the configuration for it in flink website, but did not find any solution for this. Also used kubernetes.taskmanager.node-selector=1, then pod only i am not able to see..

Could some one help with the commands to run two taskmanger in native flink in kubernetes with high availability mode.

Please find the Attached configuration used and kindly guide with the solution for it.

Thanks, 

Priyanka Manickam

[Priyanka Manickam]

Hi Yang,

Previously i have tried flink native kubernetes in default namespace without service account.

But now i have tried the flink setup in native kubernetes with newely created namespace and along with that service account . Its working now. Just wanted to share this experiment with all.

Thanks ,

Priyanka Manickam

On Mon, 12 Apr 2021, 12:26 Priyanka Manickam, <[hidden email]> wrote:

Good Day Yang

Thanks for your early response.

I do have tried the configuration mentioned in the previous reply with parallelism 8 and -Dtaskmanager.numberOfTaskSlots=4.

But still seeing only one task manager is running in azure kubernetes.

Could you please check this one and guide us if any configuration i have missed out or to be added.

Thanks,

Priyanka Manickam

On Mon, 12 Apr 2021, 12:05 Yang Wang, <[hidden email]> wrote:

Hi Priyanka Manickam,

If you are using the native Kubernetes integration, the TaskManagers will be started/stopped dynamically on demands.

It also means you could not control the number of running TaskManager pods. Refer to here[1] for more information.

In your case, numOfTaskSlots has been configured to 25 and the default parallelism is 8, so the second TaskManager

is unnecessary. If you want to running your Flink application with two TaskManagers, please set the "taskmanager.numberOfTaskSlots"

to 4 and keep the parallelism to 8. Then you could find two started TaskManagers and without spare slots.

Please note that "kubernetes.taskmanager.node-selector" is used to start TaskManager pods on specific nodes. It

is not used to configure the number of TaskManagers. Refer to K8s documentation for more information[2].

[1]. https://flink.apache.org/2021/02/10/native-k8s-with-ha.html

[2]. https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/

Best,

Yang

Priyanka Manickam <[hidden email]> 于2021年4月10日周六 下午3:47写道：

---------- Forwarded message ---------
From: Priyanka Manickam <[hidden email]>
Date: Fri, 9 Apr 2021, 23:03
Subject: Fwd: Not able to run with two task manager in native flink in kubernetes with high availability mode
To: <[hidden email]>

---------- Forwarded message ---------
From: Priyanka Manickam <[hidden email]>
Date: Fri, 9 Apr 2021, 18:56
Subject: Not able to run with two task manager in native flink in kubernetes with high availability mode
To: <[hidden email]>

Hi all,

I am using flink deployment in azure kubernetes . The mode i have chosen is native deployment high availabilty depolyment in kubernetes.

But when i used the below configuration. I am seeing only one task manager is running.but i need to run two taskmanger. I have searched the configuration for it in flink website, but did not find any solution for this. Also used kubernetes.taskmanager.node-selector=1, then pod only i am not able to see..

Could some one help with the commands to run two taskmanger in native flink in kubernetes with high availability mode.

Please find the Attached configuration used and kindly guide with the solution for it.

Thanks, 

Priyanka Manickam