Just to add. Even in your custom rollback mechanism in order to rollback
you can check the last validated spec field to get the proper image id.
On Sun, 27 Apr 2025 at 21:07, Alex Nitavsky wrote:
> Apriori your solution make sense.
> Just keep in mind that some form of blue green deployme
ou think we might be missing?
>
> Thanks again for your help!
>
> On Sun, Apr 27, 2025 at 9:48 PM Alex Nitavsky
> wrote:
>
>> Hey,
>>
>> Did you consider to use the apache operator rollback feature? It can
>> probably cover the basic verification needs. Ge
Hey,
Did you consider to use the apache operator rollback feature? It can
probably cover the basic verification needs. Generally I would consider to
probably improve the apache operator rollback mechanism if it is not
sufficient.
If not it worth to check the blue green deployment of the operator
For those who would look for an answer, the fix is available in 1.18:
https://issues.apache.org/jira/browse/FLINK-31498
Proposed solution is not to request for TaskManagers if there are some
slots already pending.
On Thu, Jul 4, 2024 at 2:00 PM Alex Nitavsky wrote:
> Hello community,
>
&g
Hello Prabhu,
On your place I would check:
1. That there is no "state leak" in your job, because it seems that state
only accumulates for the job and is never cleaned, e.g. probably some timer
which cleans the state for some key is not configured correctly.
2. Probably you accumulate the state i
