Re: Flink 1.13.6 showing 1.13.5

2022-03-02 Thread Mika Naylor

Hi Razin,

Would you mind sharing the Kubernetes manifest you're using to deploy
this? Or which docker tag you are using? I spun up a quick example using
the docker tag 'flink:1.13.6' and the correct version was shown in the
JobManager logs and in the web-ui.

Kind regards,
Mika

On 01.03.2022 13:00, Razin Bouzar wrote:

Hello,

I am observing unexpected behavior when running Flink v1.13.6 using Docker
Desktop v4.2.0 and Kubernetes v1.21.5.

While the version installed and classpath at runtime shows 1.13.6, the UI
shows Flink 1.13.5 with commit 0ff28a7. Additionally, running `./bin/flink
--version` returns `Version: 1.13.5, Commit ID: 0ff28a7`. Screenshots are
attached below.

I have tried clearing the entire local Docker environment & resetting k8s,
but still see 1.13.5. Is there something else I need to check in the
environment?

Thank you,
Razin

[image: Screen Shot 2022-03-01 at 12.47.16 PM.png]
[image: Screen Shot 2022-03-01 at 12.55.37 PM.png]





Mika Naylor
https://autophagy.io


Re: Upgrade to flink 1.14.2 and using new Data Source and Sink API

2022-01-13 Thread Mika Naylor

Hi Daniel,

These logs look pretty normal. As for the -1 epochs, depending on which version
you're using, I think that this might apply:

"For a producer which is being initialized for the first time, the producerId 
and
epoch will be set to -1. For a producer which is reinitializing, a positive 
valued
producerId and epoch must be provided."

(From: 
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=89068820#:~:text=For%20a%20producer%20which%20is,and%20epoch%20must%20be%20provided)

I think that these logs are being created when a producer is being
initialized, likely because the logging mode is INFO, which is quite
verbose.

Kind regards,
Mika

On 13.01.2022 13:40, Daniel Peled wrote:

Hi everyone,

We have upgraded our flink version from 1.13.5 to 1.14.2
We are using the new kafkaSource and KafkaSink (instead of FlinkKafkaConsumer
and FlinkKafkaProducer)
After the upgrade, we *keep seeing* these log messages in TM logs
Is this OK ?
Are we doing something wrong ?

BR,
Danny

[image: image.png]




Mika Naylor
https://autophagy.io


Re: Cannot consum from Kinesalite using FlinkKinesisConsumer

2021-12-03 Thread Mika Naylor
-core-1.14.0.jar:1.14.0]
at
org.apache.flink.streaming.api.operators.AbstractUdfStreamOperator.close(AbstractUdfStreamOperator.java:114)
~[flink-streaming-java_2.12-1.14.0.jar:1.14.0]
at
org.apache.flink.streaming.api.operators.StreamSource.close(StreamSource.java:130)
~[flink-streaming-java_2.12-1.14.0.jar:1.14.0]
at
org.apache.flink.streaming.runtime.tasks.StreamOperatorWrapper.close(StreamOperatorWrapper.java:141)
~[flink-streaming-java_2.12-1.14.0.jar:1.14.0]
at
org.apache.flink.streaming.runtime.tasks.RegularOperatorChain.closeAllOperators(RegularOperatorChain.java:127)
~[flink-streaming-java_2.12-1.14.0.jar:1.14.0]
at
org.apache.flink.streaming.runtime.tasks.StreamTask.closeAllOperators(StreamTask.java:1035)
~[flink-streaming-java_2.12-1.14.0.jar:1.14.0]
at
org.apache.flink.streaming.runtime.tasks.StreamTask.runAndSuppressThrowable(StreamTask.java:1021)
~[flink-streaming-java_2.12-1.14.0.jar:1.14.0]
at
org.apache.flink.streaming.runtime.tasks.StreamTask.cleanUp(StreamTask.java:928)
~[flink-streaming-java_2.12-1.14.0.jar:1.14.0]
at
org.apache.flink.runtime.taskmanager.Task.lambda$restoreAndInvoke$0(Task.java:940)
~[flink-runtime-1.14.0.jar:1.14.0]
at
org.apache.flink.runtime.taskmanager.Task.runWithSystemExitMonitoring(Task.java:958)
~[flink-runtime-1.14.0.jar:1.14.0]
at
org.apache.flink.runtime.taskmanager.Task.restoreAndInvoke(Task.java:940)
~[flink-runtime-1.14.0.jar:1.14.0]
at org.apache.flink.runtime.taskmanager.Task.doRun(Task.java:766)
~[flink-runtime-1.14.0.jar:1.14.0]
at org.apache.flink.runtime.taskmanager.Task.run(Task.java:575)
~[flink-runtime-1.14.0.jar:1.14.0]
at java.lang.Thread.run(Thread.java:748) ~[?:1.8.0_292]

--
*Med Vänliga Hälsningar*
*Jonas Eyob*


Mika Naylor
https://autophagy.io