Actually, Every operator/subtask will have its own status just behind the
'RUNNING' status on the flink UI.
The status may be 'CREATED', 'DEPLOYING', 'INITING', 'RUNNING' and so on as
you could see some status in [1].
Different operators/subtasks may have different status.
After all operators/subta
When we run a job, we can see the running status of the job in the
'Running Job List' on the flink web ui. Normally, it will be in the state of
‘RUNNING’.
But when the job is just started, 'RUNNING' The status of the job does not
mean that the job is processing the data correctly, it m
Hi, To remove your address from the list, send a message to:
On Sun, 21 Aug 2022 at 9:55 PM, Venkatesh kalyan
wrote:
> want to unsubscribe .
>
Hi，To remove your address from the list, send a message to:
On Mon, 22 Aug 2022 at 4:08 PM, Sijun Yang wrote:
>
Hi，
To remove your address from the list, send a message to:
On Mon, 22 Aug 2022 at 1:42 PM, Alex Drobinsky
wrote:
> Please unsubscribe me
>
Hi Edgar,
this is how we've been doing it and it's working well.
apiVersion: flink.apache.org/v1beta1
kind: FlinkDeployment
metadata:
namespace: flink
name: redacted-job
spec:
image: flink:1.15-java11
flinkVersion: v1_15
flinkConfiguration:
taskmanager.numberOfTaskSlots: "1"
kub
Hi, thanks for the response.
We have done that, reinstall the operator after the change in values but
the logs are showing the same
Thanks
Sigalit
בתאריך יום ג׳, 23 באוג׳ 2022, 18:37, מאת Gyula Fóra :
> Hi!
>
> From your logs I see:
>
> Configuring operator to watch the following namespaces:
Also you can check if the configs are updated properly in the ConfigMap. It
should be auto-populated when you reinstall it from Helm as Gyula suggested.
*kubernetes.operator.watched.namespaces: ns1, ns2, ...*
On Tue, Aug 23, 2022 at 5:37 PM Gyula Fóra wrote:
> Hi!
>
> From your logs I see:
>
> C
I think you are right that I am just seeing "processed in-flight data" and
I was misreading the UI.
However, that raises another concern I have. When I deploy a new build that
contains changes to the classes for the in-flight data, my deployments
have failed when I restore from checkpoints (or sav
Hi!
>From your logs I see:
Configuring operator to watch the following namespaces: [JOSDK_ALL_NAMESPACES]
This means that the operator is not configured correctly for the
watched namespaces. After you change the helm values you might have to
reinstall the operator.
Cheers,
Gyula
On Mon, Aug 22
Morning all!
Recently we've been trying to migrate from some custom in-house code we've
got to manage our k8s cluster with Flink running into the recently released
operator.
However, we found an issue when parsing environment variables into the
arguments which are sent into the jobs - not being a
11 matches
Mail list logo
