Hi Gyula, Good morning! Thanks so much for your review and feedback! I absolutely agree about the problem of identifying a job vertex well enough to make more informative decisions using the custom evaluator. Would be more than happy to explore an approach for associating operators with vertex IDs if a relevant FLIP does not already exist. That said, I've been working on a few Flink Kubernetes Operator-related items that I’d like to wrap up first, so it might take me about two weeks to complete this. I hope that would work?! Looking forward to your thoughts! Thanks!
Thanks Pradeepta > On 20 Mar 2025, at 12:55 PM, Gyula Fóra <gyula.f...@gmail.com> wrote: > > Hi! > > I think this is a very nice proposal, +1 from me! > > The only practical challenge is to actually be able to identify what job > vertex is what in the job graph to make good predictions / feed in external > information but this is definitely out of scope here. > The autoscaler in general needs to have a good way to associate user code / > operators with vertex ids for these types of use-cases that we need to > investigate as a followup. > > Cheers > Gyula > > On Wed, Mar 12, 2025 at 6:24 PM Pradeepta Choudhury > <pchoudhur...@apple.com.invalid> wrote: > >> Hi All, >> >> I would like to start a discussion of FLIP-514: Custom Evaluator plugin >> for Flink Autoscaler [1]. >> >> Feel free to share your thoughts and suggestions to make this feature >> better. >> >> >> [1] >> https://cwiki.apache.org/confluence/display/FLINK/FLIP-514%3A+Custom+Evaluator+plugin+for+Flink+Autoscaler >> >> >> >> Thanks >> Pradeepta
