Oh wow, I had read that documentation so many times and I was sure that API
also expected the broadcasted side to have a key like the other side, but
that's not the case, that is already what I was thinking of. Thanks.
Regards,
Alexis.
On Wed, 12 Oct 2022, 03:42 仙路尽头谁为峰, wrote:
> Hi Alexis:
>
>
I have a streaming Flink job that runs 24/7 on a Kubernetes cluster hosted
in AWS. Every few weeks or sometimes months, the job fails down with
network errors like the following error in the logs. This is with Flink
1.14.5.
Is there anything that I can do to help my application automatically retry
The log shows that the jobmanager received a SIGTERM signal from external.
Depending on how you deploy Flink, that could be a 'kill ' command, or
a kubernetes pod removal / eviction, etc. You may want to check where the
signal came from.
Best,
Xintong
On Wed, Oct 12, 2022 at 6:26 AM Puneet Dug
Hi Alexis:
The broadcast state pattern should be done by calling connect() on the
non-broadcasted stream, with the broadcaststream as an argument.
And if the main stream is keyedStream, then the processElement function
will have access to any keyed state as normal keyedstream.
Be
Hi,
I am facing an issue where when restarting task manager after adding some
configuration changes, even though task manager restarts successfully with the
updated configuration change, is causing the leader job manager to restart as
well. Pasting the leader job manager logs here
2022-10-11
Hi everyone,
I am currently thinking about a use case for a streaming job and, while I'm
fairly certain it cannot be done with the APIs that Flink currently
provides, I figured I'd put it out there in case other users think
something like this would be useful to a wider audience.
The current broa
Hi
Totally agree, rest assured that it was some venue limitations and some
post-pandemic organizational challenges that meant no videos this year. Thanks
a lot for the feedback and please let's stay positive and not draw the wrong
conclusions.
Thanks
Jun
> On Oct 10, 2022, at 2:39 PM, guente
Currently I think that would be a mistake.
Ultimately what we have here is the culmination of us never really
considering how the numRecordsOut metric should behave for operators
that emit data to other operators _and_ external systems. This goes
beyond sinks.
This even applies to numRecordsIn
Hi Sucheth.
It's related to how you defined your GenericTypes.
You may still need to give some hints to flink if you are using complicated
generic types so what you tried may not be enough.
Could you share your generic type object ?
BTW, Maybe you could refer to [1] which I think it's similar to yo
Hello,
How to avoid flink's kryo serializer for GenericTypes ? Kryo is having some
performance issues.
Tried below but no luck.
env.getConfig().disableForceKryo();
env.getConfig().enableForceAvro();
Tried this - env.getConfig().disableGenericTypes();
getting - Generic types have been disabled
10 matches
Mail list logo
