Got it. Thanks!
On Wed, Jun 12, 2024 at 6:49 PM Zhanghao Chen
wrote:
> > Does this mean it won't trigger a checkpoint before scaling up or
> scaling down?
>
> The in-place rescaling won't do that.
>
> > Do I need the autotuning to be turned on for exactly once processing?
>
> It suffices to just
> Does this mean it won't trigger a checkpoint before scaling up or scaling
> down?
The in-place rescaling won't do that.
> Do I need the autotuning to be turned on for exactly once processing?
It suffices to just go back to the full-restart upgrade mode provided by the
operator: disable adapt
Hi Zhanghao,
If I am using the autoscaler (flink-k8s-operator) without enabling
auto-tuning, the documentation says it triggers in-place scaling without
going through a full job upgrade lifecycle. Does this mean it won't trigger
a checkpoint before scaling up or scaling down?
I am observing that
FYI This was recently fixed on the website, too.
> On 28. May 2024, at 05:05, Alexandre Lemaire wrote:
>
> Thank you!
>
>> On May 27, 2024, at 9:35 PM, Junrui Lee wrote:
>>
>> Hi Alexandre,
>>
>> You can try this link:
>> https://join.slack.com/t/apache-flink/shared_invite/zt-2jn2dlgoi-P4oQ
{
"emoji": "♥️",
"version": 1
}
Hey Salva,
Good to hear your issue has been resolved one way or another!
Thanks for confirming that this operator hash trick is working on V2 as
well.
G
On Wed, Jun 12, 2024 at 5:20 AM Salva Alcántara
wrote:
> Hey Gabor,
>
> I didn't finally need to keep compatibility with existing savepoints
Hi Salva,
Unfortunately, the state is currently incompatible between enabling TTL and
disabling TTL. This issue is tracked by this jira(
https://issues.apache.org/jira/browse/FLINK-32955) and not resolved yet.
Usually, we need to find a way to reaccumulate the state after enabled the
state ttl.
