Hello,
I am trying to debug the unbounded memory consumption by the Flink process.
The heap size of the process remains the same. The size of the RSS of the
process keeps on increasing. I suspect it might be because of RocksDB.
we have the default value for state.backend.rocksdb.memory.managed as
Hello Community,
I have a requirement to read data coming over TCP socket stream and for the
same written one custom source function reading data by TCP socket.
Job is running successfully but while trying to take a savepoint, error comes
that savepoint cannot be taken.
Is there any limitation
Hello,
Thanks for your suggestion but please confirm below.
Is it the case that TCP socket source job can’t be restored from last
checkpoint?
Rgds,
Kamal
From: Jan Lukavský
Sent: 29 June 2023 06:18 PM
To: user@flink.apache.org
Subject: Re: Flink TCP custom source - secured server socket
> .
> 3 - Not possible, the dashboards are not accessible via the internet, so
we use kube and port forward, URL looks like http://wobbegong:3/ the
port changes
Well, if the port changes, you can differentiate between the bookmarks -
just need to consistently use the same port when port forwarding
This comes up when the Schema Registry has authorization capabilities.
A producing application may not be authorized to call “register” when another
principal owns the schema subject, for example in organizations with strong
schema governance practices. When ConfluentSchemaRegistryCoder.writeSch
Thank you for your answer!
It's work right now, one more question:
I've got few streams from few Kafka topics (if it possible to do other
way and easier I could make one topic or any other modifications) with
sensors measurements into JSON messages:
topic1: {'data': {'temp':25.2, 'sensore_name':
Hi team,
I'm investigating the Flink Batch mode using Table API. And I found the OVER
clause runnable in Steaming mode has some issues in batch mode. The stacktrace
is that the RangeBoundComparator class generated has compile issue.
I attached the complete error in the end. Look forward to ge
Hi all,
It's really a bug, haishui has created the FLINK-32496[1],
let's follow this issue there.
[1] https://issues.apache.org/jira/browse/FLINK-32496
Best,
Rui Fan
On Thu, Jun 29, 2023 at 8:34 PM Alexis Sarda-Espinosa <
sarda.espin...@gmail.com> wrote:
> BTW, it seems I spoke too soon in my
