flink-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yang Wang <danrtsey...@gmail.com>
Subject Re: Native K8S not creating TMs
Date Mon, 08 Jun 2020 03:02:40 GMT
Hi Kevin,

It may because the characters length limitation of K8s(no more than 63)[1].
So the pod
name could not be too long. I notice that you are using the client
automatic generated
cluster-id. It may cause problem and could you set a meaningful cluster-id
for your Flink
session? For example,

kubernetes-session.sh ... -Dkubernetes.cluster-id=my-flink-k8s-session

This behavior has been improved in Flink 1.11 to check the length in client
side before submission.

If it still could not work, could you share your full command and
jobmanager logs? It will help a lot
to find the root cause.


[1].
https://stackoverflow.com/questions/50412837/kubernetes-label-name-63-character-limit


Best,
Yang

kb <Kevin_Bohinski@comcast.com> 于2020年6月6日周六 上午1:00写道:

> Thanks Yang for the suggestion, I have tried it and I'm still getting the
> same exception. Is it possible its due to the null pod name? Operation:
> [create]  for kind: [Pod]  with name: [null]  in namespace: [default]
> failed.
>
> Best,
> kevin
>
>
>
> --
> Sent from:
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
>

Mime
View raw message