I second Yangze's suggestion. You need to get the jobmanager log first. Then it will be easier to find the root cause. I know that it is not convenient for users to access the log via kubectl and we already have a ticket for this[1].
Usually, the reason that Flink resourcemanager could not allocate taskmanagers from K8s is the service account not configured correctly. You could checkout the RBAC configuration here[2]. [1]. https://issues.apache.org/jira/browse/FLINK-15792 [2]. https://ci.apache.org/projects/flink/flink-docs-release-1.10/ops/deployment/native_kubernetes.html#rbac Best, Yang Yangze Guo <karma...@gmail.com> 于2020年6月4日周四 上午10:01写道： > Amend: for release 1.10.1, please refer to this guide [1]. > > [1] > https://ci.apache.org/projects/flink/flink-docs-release-1.10/ops/deployment/native_kubernetes.html#log-files > > Best, > Yangze Guo > > On Thu, Jun 4, 2020 at 9:52 AM Yangze Guo <karma...@gmail.com> wrote: > > > > Hi, Kevin, > > > > Regarding logs, you could follow this guide [1]. > > > > BTW, you could execute "kubectl get pod" to get the current pods. If > > there is something like "flink-taskmanager-1-1", you could execute > > "kubectl describe pod flink-taskmanager-1-1" to see the status of it. > > > > [1] > https://ci.apache.org/projects/flink/flink-docs-master/ops/deployment/native_kubernetes.html#log-files > > > > Best, > > Yangze Guo > > > > On Thu, Jun 4, 2020 at 2:28 AM kb <kevin_bohin...@comcast.com> wrote: > > > > > > Hi > > > > > > We are using 1.10.1 with native k8s and while the service appears to be > > > created and I can submit a job & see it via Web UI, TMs/pods are never > > > created thus the jobs never start. > > > > > > > org.apache.flink.runtime.jobmanager.scheduler.NoResourceAvailableException: > > > Could not allocate the required slot within slot request timeout. > Please > > > make sure that the cluster has enough resources. > > > > > > Is there somewhere I could see the pod creation logs? > > > > > > thanks > > > > > > > > > > > > -- > > > Sent from: > http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/ >
