Got it, thanks @Gyula F贸ra<mailto:gyula.f...@gmail.com> 馃槉

From: Gyula F贸ra <gyula.f...@gmail.com>
Sent: Friday, January 13, 2023 12:09 PM
To: Swathi Chandrashekar <cswa...@microsoft.com>
Cc: Chesnay Schepler <ches...@apache.org>; Tamir Sagi 
<tamir.s...@niceactimize.com>; user@flink.apache.org
Subject: Re: [EXTERNAL] Re: Flink reactive mode for application clusters on AWS 
EKS

What I am trying to say is use the Kubernetes operator with Native (default) 
mode and forget about reactive .

The operator does everything you wwant plus has an actual autoscaler.

Gyula

On Fri, 13 Jan 2023 at 07:24, Swathi Chandrashekar 
<cswa...@microsoft.com<mailto:cswa...@microsoft.com>> wrote:
Got it, so this means, we should have standalone app mode cluster which is 
managed by a flink Kubernetes operator and the operator would update the 
replicas based on the metrics ( autoscale ) which in-tern changes the 
parallelism as reactivemode is enabled.

Regards,
Swathi C

From: Gyula F贸ra <gyula.f...@gmail.com<mailto:gyula.f...@gmail.com>>
Sent: Friday, January 13, 2023 11:31 AM
To: Swathi Chandrashekar <cswa...@microsoft.com<mailto:cswa...@microsoft.com>>
Cc: Chesnay Schepler <ches...@apache.org<mailto:ches...@apache.org>>; Tamir 
Sagi <tamir.s...@niceactimize.com<mailto:tamir.s...@niceactimize.com>>; 
user@flink.apache.org<mailto:user@flink.apache.org>
Subject: Re: [EXTERNAL] Re: Flink reactive mode for application clusters on AWS 
EKS

No but the Kubernetes operator itself already provides similar feature set.

Not sure why you want the reactive mode in the first place . If it's because 
you want to implement auto scaling on top of it, then I think the operator is a 
better alternative.

I think you should try to understand what exactly the reactive mode provides vs 
what the operator does. Reactive mode alone doesn鈥檛 do too much.

Gyula

On Fri, 13 Jan 2023 at 06:33, Swathi Chandrashekar 
<cswa...@microsoft.com<mailto:cswa...@microsoft.com>> wrote:
Hi @Gyula F贸ra<mailto:gyula.f...@gmail.com>,

Does this mean, with Kubernetes operator, we can have reactive mode in native 
flink which is in app mode ? [ Not just standalone app mode ]

Regards,
Swathi C

From: Gyula F贸ra <gyula.f...@gmail.com<mailto:gyula.f...@gmail.com>>
Sent: Thursday, January 12, 2023 11:14 PM
To: Tamir Sagi <tamir.s...@niceactimize.com<mailto:tamir.s...@niceactimize.com>>
Cc: Chesnay Schepler <ches...@apache.org<mailto:ches...@apache.org>>; 
user@flink.apache.org<mailto:user@flink.apache.org>
Subject: [EXTERNAL] Re: Flink reactive mode for application clusters on AWS EKS

Hey!

I think the reactive scaling is a somewhat misunderstood feature. It only works 
in standalone deployments (not in Kubernetes native for instace) and it doesn't 
actually provide any autoscaling functionality on its own.
You would have to implement your scaling logic yourself somehow (Kubernetes HPA 
or something similar)

I suggest looking at the Flink Kubernetes Operator 
(https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnightlies.apache.org%2Fflink%2Fflink-kubernetes-operator-docs-main%2F&data=05%7C01%7Ccswathi%40microsoft.com%7C233ccdc42b3b45cc63cf08daf530eef2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638091887810148204%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=FctuG6R%2FtbryPSBunY1onzrOLwFFvXj671WQVNni%2Fhc%3D&reserved=0>)
 that will provide actual autoscaler capability for native Kubernetes 
deployments.

Cheers,
Gyula

On Thu, Jan 12, 2023 at 6:23 PM Tamir Sagi 
<tamir.s...@niceactimize.com<mailto:tamir.s...@niceactimize.com>> wrote:
Hey Chesnay,

Just to be more clear,
I'm talking about plans to support reactive mode for application clusters in 
Native Kubernetes.

https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/#application-mode<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnightlies.apache.org%2Fflink%2Fflink-docs-master%2Fdocs%2Fdeployment%2Fresource-providers%2Fnative_kubernetes%2F%23application-mode&data=05%7C01%7Ccswathi%40microsoft.com%7C233ccdc42b3b45cc63cf08daf530eef2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638091887810148204%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=OPFvgaDKzKwuoD1E0xiwGqcTnxUwk3Bv04Av1dGket4%3D&reserved=0>

Thanks,
Tamir.

________________________________
From: Tamir Sagi 
<tamir.s...@niceactimize.com<mailto:tamir.s...@niceactimize.com>>
Sent: Thursday, January 12, 2023 6:17 PM
To: Chesnay Schepler <ches...@apache.org<mailto:ches...@apache.org>>; 
user@flink.apache.org<mailto:user@flink.apache.org> 
<user@flink.apache.org<mailto:user@flink.apache.org>>
Subject: Re: Flink reactive mode for application clusters on AWS EKS

Hey Chesnay,

Thank you for your response.

Since we are running our Flink jobs on EKS (Elastic Kubernetes Service)  I was 
asking regarding Application cluster on Kubernetes.

The documentations I referred to clearly state that it is not supported, the 
same as shown on Flink website.

[cid:image001.png@01D9274A.1DEF1050]
Is there any plan to support that anytime soon?

Thanks

Tamir.
________________________________
From: Chesnay Schepler <ches...@apache.org<mailto:ches...@apache.org>>
Sent: Thursday, January 12, 2023 4:30 PM
To: Tamir Sagi 
<tamir.s...@niceactimize.com<mailto:tamir.s...@niceactimize.com>>; 
user@flink.apache.org<mailto:user@flink.apache.org> 
<user@flink.apache.org<mailto:user@flink.apache.org>>
Subject: Re: Flink reactive mode for application clusters on AWS EKS


EXTERNAL EMAIL

The adaptive scheduler and reactive mode both already support application 
clusters since 1.13.

https://nightlies.apache.org/flink/flink-docs-release-1.16/docs/deployment/elastic_scaling/<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnightlies.apache.org%2Fflink%2Fflink-docs-release-1.16%2Fdocs%2Fdeployment%2Felastic_scaling%2F&data=05%7C01%7Ccswathi%40microsoft.com%7C233ccdc42b3b45cc63cf08daf530eef2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638091887810148204%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=WxxeXDNPkwG1AbI1Con8u%2Fhuwk6e8zHkCpc4K8GYodU%3D&reserved=0>

On 19/12/2022 10:17, Tamir Sagi wrote:
Hey,

We are running stream jobs on application clusters (v1.15.2) on AWS EKS.

I was reviewing the following pages on Flink confluence

  *   Reactive mode [1]
  *   Adaptive Scheduler [2]
I also encountered the following POC conducted by Robert Metzger 
(@rmetzger_<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2Frmetzger_&data=05%7C01%7Ccswathi%40microsoft.com%7C233ccdc42b3b45cc63cf08daf530eef2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638091887810148204%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3dFfjD3VoC0xQCN8qnVIAgRelR89ZM0Qf7wj2mFiEcI%3D&reserved=0>)
 on 06 May 2021. [3]

my question is whether that feature will be supported in the future for 
application clusters or not.

[1] 
https://cwiki.apache.org/confluence/display/FLINK/FLIP-159%3A+Reactive+Mode<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FFLINK%2FFLIP-159%253A%2BReactive%2BMode&data=05%7C01%7Ccswathi%40microsoft.com%7C233ccdc42b3b45cc63cf08daf530eef2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638091887810148204%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=pIBeCzno2%2Ba5FRfuWAN2g7bFh2OLU2xdG%2FgoK8HaXEM%3D&reserved=0>
[2] 
https://cwiki.apache.org/confluence/display/FLINK/FLIP-160%3A+Adaptive+Scheduler<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FFLINK%2FFLIP-160%253A%2BAdaptive%2BScheduler&data=05%7C01%7Ccswathi%40microsoft.com%7C233ccdc42b3b45cc63cf08daf530eef2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638091887810148204%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=fl4fEoJolQ1wxvg2U4skGXnlOaaT4c%2BQesFlLhoknwc%3D&reserved=0>
[3] 
https://flink.apache.org/2021/05/06/reactive-mode.html<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fflink.apache.org%2F2021%2F05%2F06%2Freactive-mode.html&data=05%7C01%7Ccswathi%40microsoft.com%7C233ccdc42b3b45cc63cf08daf530eef2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638091887810148204%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=6Tiu4atMzazTMsRo9GJxKEXRDTWh2hn4LrT4NbHzPeg%3D&reserved=0>


Thanks,
Tamir.


Confidentiality: This communication and any attachments are intended for the 
above-named persons only and may be confidential and/or legally privileged. Any 
opinions expressed in this communication are not necessarily those of NICE 
Actimize. If this communication has come to you in error you must take no 
action based on it, nor must you copy or show it to anyone; please 
delete/destroy and inform the sender by e-mail immediately.
Monitoring: NICE Actimize may monitor incoming and outgoing e-mails.
Viruses: Although we have taken steps toward ensuring that this e-mail and 
attachments are free from any virus, we advise that in keeping with good 
computing practice the recipient should ensure they are actually virus free.



Confidentiality: This communication and any attachments are intended for the 
above-named persons only and may be confidential and/or legally privileged. Any 
opinions expressed in this communication are not necessarily those of NICE 
Actimize. If this communication has come to you in error you must take no 
action based on it, nor must you copy or show it to anyone; please 
delete/destroy and inform the sender by e-mail immediately.
Monitoring: NICE Actimize may monitor incoming and outgoing e-mails.
Viruses: Although we have taken steps toward ensuring that this e-mail and 
attachments are free from any virus, we advise that in keeping with good 
computing practice the recipient should ensure they are actually virus free.

Confidentiality: This communication and any attachments are intended for the 
above-named persons only and may be confidential and/or legally privileged. Any 
opinions expressed in this communication are not necessarily those of NICE 
Actimize. If this communication has come to you in error you must take no 
action based on it, nor must you copy or show it to anyone; please 
delete/destroy and inform the sender by e-mail immediately.
Monitoring: NICE Actimize may monitor incoming and outgoing e-mails.
Viruses: Although we have taken steps toward ensuring that this e-mail and 
attachments are free from any virus, we advise that in keeping with good 
computing practice the recipient should ensure they are actually virus free.

Reply via email to