Hi,
Currently i am working with flink HA cluster with 3 job managers and 3
zookeeper nodes. Also i am persisting my checkpoints to s3 and hence already
configured required flink-s3 jars during flink job manager and task manager
process startup. Now i have configured a variable
web.upload.dir
Sorry for the late reply.
Flink clients will ship the log4j-console.properties and
logback-console.xml via K8s ConfigMap and then mount to
JobManager/TaskManager pod.
So if you want to update the log settings or using logback, all you need is
to update the client-local files.
Best,
Yang
Ragha
Hi. Any updates on this?
How do people usually do TTLs? I want to add a backup TTL in case I have
leaky state.
On Wed, Jun 17, 2020 at 6:08 AM Andrey Zagrebin
wrote:
> Hi Arti,
>
> Any program can use State with TTL but the state can only expire in
> processing time at the moment even if you
Hi Mariam,
1. The expired state object will be cleaned up when it is accessed in a read
operation. And for the expired state that is never accessed again, there are
three strategies to remove it in the background: FULL_STATE_SCAN_SNAPSHOT,
INCREMENTAL_CLEANUP, ROCKSDB_COMPACTION_FILTER.
2. FULL
Maybe the Flink applications could run more stably if you configure enough
resources(e.g. memory, cpu, ephemeral-storage) for the JobManager and
TaskManager pods.
Best,
Yang
David Morávek 于2022年1月5日周三 16:46写道：
> Hi Tianyi,
>
> this really depends on your kubernetes setup (eg. if autoscaling is
+1 for dropping the MapR Fs.
Best
Yun Tang
From: Till Rohrmann
Sent: Wednesday, January 5, 2022 18:33
To: Martijn Visser
Cc: David Morávek ; dev ; Seth Wiesman
; User
Subject: Re: [DISCUSS] Deprecate MapR FS
+1 for dropping the MapR FS.
Cheers,
Till
On Wed,
Thanks all for this fruitful discussion.
I think Xintong has given a strong point why we introduced the native K8s
integration, which is active resource management.
I have a concrete example for this in the production. When a K8s node is
down, the standalone K8s deployment will take longer
recover
The statefun project currently references Flink 1.13.2. Is 1.13.2 the
*minimum *Flink version required, i.e. would Statefun be expected to work
with Flink 1.14.2 or whatever the latest released version is, as well? Or
is it important to use exactly version 1.13.2 of Flink? Thanks.
Are there any plans for Flink to support Java 17 and provide Java 17-based
Docker images?
There are a variety of new language/VM features we'd like to use and we
were hoping Flink would support Java 17.
thanks
Kurt
Hello,
as I am confused that in my tests the Exception on restoring keyed state backend only happens on scale-in/node-fail and not in scale-out, I re-run the scale-out test case.And indeed, there the exception by HeapKeyedStateBackendBuilder does not happen, and restoring keyed state backend works
Flink community officially only supports current and previous minor
versions [1] (1.13, 1.14) with bug fixes. Personally I wouldn’t expect
there will be another patch release for 1.12.
If you really need an extra release for the unsupported version, the most
straightforward approach would be manua
Hi David,
As per the below comments, Flink 1.14.3 is in preparation and this hasn't
started yet for Flink 1.13.6. Flink 1.12.8 release will be planned after this?
If there is no current plan, could you please let us know what will be the
regular release timing for 1.12.8 version.
Regards,
Such
Dear All,
I am writing to inquire about the state time to live lazy removal. I guess
that even if the state has expired it i still in the memory and not garbage
collected. The question is how to get rid of those expired states.
Best regards,
Mariam
13 matches
Mail list logo
