Hi all,
We’ve upgraded from Flink 1.11 to 1.13, and our workflows are now sometimes
failing with an exception, even though the job has succeeded.
The stack trace for this bit of the exception is:
java.util.concurrent.ExecutionException:
org.apache.flink.runtime.concurrent.FutureUtils$RetryExce
Looks like after script *flink-daemon.sh *complete, it return exit 0.
Kubernetes regard it as done. Is that expected?
Thanks,
Qihua
On Thu, Sep 30, 2021 at 11:11 AM Qihua Yang wrote:
> Thank you for your reply.
> From the log, exit code is 0, and reason is Completed.
> Looks like the cluster is
Thank you for your reply.
>From the log, exit code is 0, and reason is Completed.
Looks like the cluster is fine. But why kubenetes restart the pod. As you
said, from perspective of Kubernetes everything is done. Then how to
prevent the restart?
It didn't even give chance to upload and run a jar...
I did check the kubectl describe, it shows below info. Reason is Completed.
Ports: 8081/TCP, 6123/TCP, 6124/TCP, 6125/TCP
Host Ports:0/TCP, 0/TCP, 0/TCP, 0/TCP
Command:
/opt/flink/bin/entrypoint.sh
Args:
/opt/flink/bin/run-job-manager.sh
State:
Hi all,
We're debugging an issue with OOMs that occurs on our jobs shortly after a
restore from checkpoint. Our application is running on kubernetes and uses
RocksDB as it's state backend.
We reproduced the issue on a small cluster of 2 task managers. If we killed
a single task manager, we notice
We only support zk 3.4/3.5 .
To try another ZK version you will need to create a
flink-shaded-zookeeper artifact, similar to the 3.4/3.5 version that you
can find here:
https://github.com/apache/flink-shaded/tree/master/flink-shaded-zookeeper-parent
Once you have that it theoretically is as
Hi Matthias, the log file is quite large (21MB) so mailing it over in its
entirety may have been a challenge. The file is available here [1], and we’re
of course happy to share any relevant parts of it with the mailing list.
I think since we’ve shared logs with you before in the past, you weren’
@Matthias Pohl : I've also been annoyed by this 30
days limit, but I'm not aware of a way to globally change the default. I
would ask in #asfinfra in the asf slack.
On Thu, Sep 30, 2021 at 12:19 PM Till Rohrmann wrote:
> Thanks for the hint with the managed search engines Matthias. I think this
Hi ,
Does Flink 1.12.2 support Zookeeper version 3.6+ ?
If we add zookeeper version 3.6 jar in the flink image ,would it be able
to connect ?
The following link mentions only zk 3.5 or 3.4
https://ci.apache.org/projects/flink/flink-docs-master/docs/deployment/ha/zookeeper_ha/#zookeeper-versions
Thanks for the hint with the managed search engines Matthias. I think this
is quite helpful.
Cheers,
Till
On Wed, Sep 15, 2021 at 4:27 PM Matthias Pohl
wrote:
> Thanks Leonard for the announcement. I guess that is helpful.
>
> @Robert is there any way we can change the default setting to someth
Hi,
If you're new to k8s you can try to use Flink Native[1]. It's a CLI tool
that can be used to deploy Flink in application mode or session mode but
note that Reactive Mode is not supported in Flink Native.
To answer your questions
a) You need to bundle your jar with the Flink image or mount it
Is the run-job-manager.sh script actually blocking?
Since you (apparently) use that as an entrypoint, if that scripts exits
after starting the JM then from the perspective of Kubernetes everything
is done.
On 30/09/2021 08:59, Matthias Pohl wrote:
Hi Qihua,
I guess, looking into kubectl descr
Hi Guys
I've just recently started using Apache Flink to evaluate its suitability
for a project I'm working on.
First impressions are that the project is great, well documented and has
lots of examples and guidance showcasing the multitude of things that it
can do. Challenging knowing where to s
Thanks for sharing. I was wondering why you don't use $PORT0 in your
command. And: Are the ports properly configured in the Marathon network
configuration [1]? But the error seems to be unrelated to that setting.
Other than that, I cannot see any other issue with the configuration. It
could be that
Hi Qihua,
I guess, looking into kubectl describe and the JobManager logs would help
in understanding what's going on.
Best,
Matthias
On Wed, Sep 29, 2021 at 8:37 PM Qihua Yang wrote:
> Hi,
> I deployed flink in session mode. I didn't run any jobs. I saw below logs.
> That is normal, same as Fli
15 matches
Mail list logo
