> I think this is a general issue with the Flink metrics.
Not quite. There are a few instance in Flink were code wasn't updated to
encode metadata as additional labels, and the RocksDB metrics may be one
of them.
Also for RocksDB, you could try setting
"state.backend.rocksdb.metrics.column-fam
Hello,
We are running Flink jobs on K8s and using RocksDB as state backend. It is
connected to S3 for checkpointing. We have multiple states in the job (mapstate
and value states). We are seeing a slow but stable increase over time on the
memory consumption. We only see this in our jobs connect
Hello,
We're experiencing difficulties in using Flink metrics in a generic way
since various properties are included in the name of the metric itself.
This makes it difficult to generate sensible (and general) dashboards (with
aggregations).
One example is the metric for rocksdb estimated live da
Building your own custom operator image is also fairly straightforward and
is also a good exercise to make sure you can easily backport critical fixes
into your prod envs in the future :)
Cheers,
Gyula
On Tue, Oct 17, 2023 at 10:48 AM Niklas Wilcke
wrote:
> Hi Gyula,
>
> thank you very much for
Hi Gyula,
thank you very much for the update about the release schedule and for pointing
me to the snapshot images. This is indeed very helpful and we will consider our
options now.
Regards,
Niklas
> On 16. Oct 2023, at 17:56, Gyula Fóra wrote:
>
> Hi Niklas!
>
> We weren't planning a 1.6.1
