Hello community,
We're making use of uid method on all the stateful operators to assign
custom operator id's.
However, I don't see any reference to these operator id's anywhere in the
job logs or Flink UI or even checkpoint details.
Do I need to look into some other place?
Thanks,
Megh
Yes, that also works correctly, at least based on the Kafka source we use
(we'd get an alert if it suddenly started consuming from a very old offset).
Regards,
Alexis.
On Thu, 5 Oct 2023, 19:36 ramkrishna vasudevan,
wrote:
> Sorry for the late reply. Just in case you restart the job , is it abl
Hey,
We don’t have minimal supported version in the docs as we haven’t
experienced any issue specific to kubernetes versions so far.
We don’t really rely on any newer features
Cheers
Gyula
On Fri, 6 Oct 2023 at 06:02, Krzysztof Chmielewski <
krzysiek.chmielew...@gmail.com> wrote:
> It seems t
Hi team,
I have one question, hoping to get some help.
Will BoundedOutOfOrderness have any impact on the KeyedProcessFunction? If so,
in what way it can impact KeyedProcessFunction?
Thanks!
Best,
Lijuan
It seems that problem was caused by k8s 1.19.
When we deployed Flink operator on vanilla k8s 1.19 we got the same error
that we have on OKD 4.6.0 We are planing to update OKD to newer version
that will use more up to date k8s.
What is the minimal k8s version required for/supported by Flink operato
Hi Tony!
There are still a few corner cases when the operator cannot upgrade /
rollback deployments due to the loss of HA metadata (and with that
checkpoint information).
Most of these issues are not related to the operator logic directly but to
how Flink handles certain failures and are related
After digging into the flink-python code, It seems if
`PYFLINK_GATEWAY_DISABLED` is set to false in an environment variable, then
using Types.LIST(Types.ROW([...])) does not have any issue, once Java
Gateway is launched.
It was unexpected for Flink local run to set this flag to false explicitly.
Sorry for the late reply. Just in case you restart the job , is it able to
safely use the checkpoint and get back to the checkpointed state?
Regards
Ram,
On Thu, Sep 28, 2023 at 4:46 PM Alexis Sarda-Espinosa <
sarda.espin...@gmail.com> wrote:
> Hi Surendra,
>
> there are no exceptions in the log
I tried this out with operator version 1.4 and it didn't work for me. I
noticed that when I was deploying a bad version, the Kubernetes HA metadata
and configmaps were deleted:
[m [33m2023-10-05 14:52:17,493 [m [36mo.a.f.k.o.l.AuditUtils [m [32m[INFO
][flink-testing-service/flink-testing-service]
I just saw this experimental feature in the documentation:
https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/docs/custom-resource/job-management/#application-upgrade-rollbacks-experimental
I'm guessing this is the only way to automate rollbacks for now.
On Wed, Oct 4, 2023 at
Hello Experts,
I have developed a couple of modules where one of the modules is getting
data from Kafka, applying the process window function, and getting the
required form of data. However, I went through the official documentation
and there are no approaches for implementing the unit test cases
11 matches
Mail list logo
