[
https://issues.apache.org/jira/browse/FLINK-23006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17364730#comment-17364730
]
Till Rohrmann commented on FLINK-23006:
---------------------------------------
Are you sure that {{historyserver.web.address: http://flinkhistory:8082}} can
be resolved from within the pod? You should rather bind the history server to
{{0.0.0.0}}.
A general note: Please do not open blocker issues for user questions. Almost
all of your tickets are questions about using Flink and not real problems. Most
of them even seem to come from not properly understanding Kubernetes. Please
ask these questions on the user mailing list instead.
> issue in configuring History server
> ------------------------------------
>
> Key: FLINK-23006
> URL: https://issues.apache.org/jira/browse/FLINK-23006
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Kubernetes
> Affects Versions: 1.13.1
> Reporter: Bhagi
> Priority: Blocker
> Attachments: flink-history-server-7fb6f9b66-bkhfm.log,
> history-server-deployment.yaml
>
>
> Dear Team,
> I have flink session cluster with HA on standalone kubernetes. I want to
> configure History server for this flink cluster..
> to configure the history server, in the Flink cluster name space i created 1
> more deployment for history server by passing args: ["history-server"], but
> pod is in carshloopBackoff.
> can you see the logs of this and help me to configure history server.
> kubectl get po -n flink-load-test
> NAME READY STATUS RESTARTS
> AGE
> flink-history-server-7fb6f9b66-bkhfm 0/1 CrashLoopBackOff 10
> 29m
> flink-jobmanager-7df744b455-f575q 1/1 Running 0
> 18h
> flink-jobmanager-7df744b455-qm6wf 1/1 Running 0
> 18h
> flink-jobmanager-7df744b455-t7zm5 1/1 Running 1
> 18h
> flink-taskmanager-7945f6b856-89mr5 1/1 Running 7
> 18h
> flink-taskmanager-7945f6b856-mz2hz 1/1 Running 7
> 18h
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
