[
https://issues.apache.org/jira/browse/FLINK-34179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil_D updated FLINK-34179:
-----------------------------
Description: Deployed flink in aws eks cluster using bitnami helm chart
(bitnami/flink 1.18). After deployment, noticing that out of 5 taskmanager pods
only one taskmanager pod is able to connect to resourcemanager which is present
in jobmanager. (was: Deployed flink in aws eks cluster using bitnami helm
chart. After deployment, noticing that out of 5 taskmanager pods only one
taskmanager pod is able to connect to resourcemanager which is present in
jobmanager.)
> More than one taskmanager is not coming up in flink (session mode) in aws eks
> cluster
> -------------------------------------------------------------------------------------
>
> Key: FLINK-34179
> URL: https://issues.apache.org/jira/browse/FLINK-34179
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Kubernetes
> Affects Versions: 1.18.0
> Reporter: Nikhil_D
> Priority: Blocker
> Labels: flink-k8s
> Attachments: flink-uxxx-taskmanager-8b69df9d7-xxnbn.log,
> flink-values.yaml
>
>
> Deployed flink in aws eks cluster using bitnami helm chart (bitnami/flink
> 1.18). After deployment, noticing that out of 5 taskmanager pods only one
> taskmanager pod is able to connect to resourcemanager which is present in
> jobmanager.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
