I am not aware that we use Nessus. We are running on Google Cloud Dataproc
vanilla. On the other hand, Flink restarted from a checkpoint and reread
the Kafka offset and didn't encounter this error again, so if it was
something in the input I would expect it to happen again when it processes
the Kaf
One other pointer: Martijn mentioned in FLINK-24923 [1] tools like Nessus
could generate traffic while scanning for ports. It's just the size of the
request that is suspicious.
[1] https://issues.apache.org/jira/browse/FLINK-24923
On Thu, Mar 17, 2022 at 5:29 PM Ori Popowski wrote:
> This issue
This issue did not repeat, so it may be a network issue
On Thu, Mar 17, 2022 at 6:12 PM Matthias Pohl wrote:
> Hi Ori,
> that looks odd. The message seems to exceed the maximum size of 2147483647
> bytes (2GB). I couldn't find anything similar in the ML or in Jira that
> supports a bug in Flink.
Hi Ori,
that looks odd. The message seems to exceed the maximum size of 2147483647
bytes (2GB). I couldn't find anything similar in the ML or in Jira that
supports a bug in Flink. Could it be that there was some network issue?
Matthias
On Tue, Mar 15, 2022 at 6:52 AM Ori Popowski wrote:
> I am
