The reactive mode reacts to available resources. The autoscaler reacts to
changing load and processing capacity and adjusts resources.
Completely different concepts and applicability.
Most people want the autoscaler , but this is a recent feature and is
specific to the k8s operator at the moment.
Hi thanks,
However what you have send me is sql client. I'm looking for a way to do it
via k8s operator's java Api.
pt., 1 wrz 2023, 03:58 użytkownik Shammon FY napisał:
> Hi Krzysztof,
>
> For the flink session cluster, you can stop the job with savepoint through
> the statement `STOP JOB '{You
Hello,
Thanks for your notice.
Than what is the purpose of using 'reactive', if this doesn't do anything
itself?
What is the difference if I use auto-scaler without 'reactive' mode?
Regards,
Jung
2023년 8월 18일 (금) 오후 7:51, Gyula Fóra 님이 작성:
> Hi!
>
> I think what you need is probably not the r
Hi Krzysztof,
For the flink session cluster, you can stop the job with savepoint through
the statement `STOP JOB '{Your job id}' WITH SAVEPOINT;`. You can refer to
[1] for more information about how to do it in sql client and you can also
create a table environment to perform the statement in your
Hi community,
I would like to ask what is the recommended way to stop Flink job with save
point on a session cluster via k8s operator Java API?
Currently I'm doing this by setting savepointTriggerNonce on JobSpec object.
However I've noticed that this works only if I do not include Job state
chang
Hi,
Thanks for the info.
I updated my code implementation. I am producing a list in my
custom processAllWindowFunction() before it goes to my customSink. The
problem I get is the list doesnt get reset/cleared.
inputStream.
windowAll(TumblingProcessingTimeWindows.of(Time.of(Time.seconds(10)))
.t
There is no effect of the replicas setting in native mode. Native session
clusters are "elastic", the number of task managers are determined on the
fly based on the job requirements.
Gyula
On Thu, Aug 31, 2023 at 11:19 AM Krzysztof Chmielewski <
krzysiek.chmielew...@gmail.com> wrote:
> Thank you
Thank you for the response.
Yes currently in my PoC I'm using standalone integration.
Does ` spec.taskManager.replicas` has any effect when using native mode?
The reason I'm asking is that I need to know what is the "cacpacity" of
particular session cluster before I will submit the job into it.
A
I guess your question is in the context of the standalone integration
because native session deployments automatically add TMs on the fly as more
are necessary.
For standalone mode you should be able to configure
`spec.taskManager.replicas` and if I understand correctly that will not
shut down the
Definitely our intent is to start with an in house specific Blue Green
operator and once we will reach some level of confidence we will open a
FLIP to discuss it.
Nicolas
On Thu, Aug 31, 2023 at 10:12 AM Gyula Fóra wrote:
> The main concern as we discussed in previous mailing list threads befor
The main concern as we discussed in previous mailing list threads before is
the general applicability of such solution:
- Many production jobs cannot really afford running in parallel (starting
the second job while the first one is running), due to data
consistency/duplications reasons
- Exactly
Thanks Gyula for your feedback.
We were also thinking of relying on such a solution, creating a dedicated
crd/operator to manage this BlueGreenFlinkDeployment.
Good to hear that it could be incorporated later in the operator.
Will let you know once we will have something to share with you.
Nicol
12 matches
Mail list logo
