Hi team, is it possible to provision standby taskm...
# troubleshooting
j
Hi team, is it possible to provision standby taskmanagers with FlinkDeployment for quick recovery?
馃憖 1
g
With standalone mode , probably , but not with native mode as far as I know :)
But it would be a nice feature to add to Flink for the native mode :)
j
I tried with standalone but it also resets parallelism based on TM replicas 馃槥
g
Ah yea right, those are connected with a single equation
j
馃檪
g
Maybe this is worth a jira ticket, we could add support for standalone mode through the operator
And another ticket for adding this to native as well but that needs to go in Flink :)
j
Will create two. Thanks!
g
The standalone one is an easy fix if you want to give it a shot
Is that's the right place to get number of TMs?
g
Yes but we need an extra conf for the standby tm num
And then we can adjust the parallelism calculation
j
so above code is not used for native mode
g
No it's not
j
I thought in native mode also if replicas is set for TM operator resets parallelism
g
That's true but the JM creates tms on demand
So it's impossible to get standbys
j
oh ok 馃憤
k
is there a way to change the taskmanager parallelism value in runtime?
g
The operator does this with standalone mode and reactive scaling enabled to scale jobs
But reactive mode is not very stable I feel
k
great will check out, any other alternate way in flink kubernetes operator?
g
Why do you want to do this? The operator does things for specific reasons usually :)
k
to do manual scaling when required without reinstalling the helmchart
g
doesn鈥檛 really sound like a use-case we want to support through the operator. If you want to rescale a deployment, you change the spec and the operator should execute this in the most efficient way
k
How I can change that through operator
g
You can try enabling this config for native deployments
j
Cool, let me take a look gratitude thank you
Copy code
The number of redundant task managers. Redundant task managers are extra task managers started by Flink, in order to speed up job recovery in case of failures due to task manager lost. Note that this feature is available only to the active deployments (native K8s, Yarn).
The description says
this feature is available only to the active deployments  (native K8s, Yarn)
. Does that mean it is available in
mode: native
?
g
yes
馃憤 1
j
We tried this with Flink 1.15. What we noticed is while adding redundant TMs a node scaling is triggered (which will take few minutes). As redundant TMs are not ready in some configured time, flink tries to keep adding more redundant TMs until it gets needed TMs in ready state. For each new provisioning of redundant TM job is getting restarted. Once it settled down we had 17 extra redundant TMs (request was 2) and then 15 of them removed. Is there any config that you know can control the time interval of spinning new redundant TMs?
g
I never tried this so I know very little about it :/
j
No worries, thanks 馃檪