[
https://issues.apache.org/jira/browse/FLINK-20206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-20206:
-----------------------------------
Labels: auto-deprioritized-major stale-minor usability (was:
auto-deprioritized-major usability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Failed to start the session, but there is no clear prompt.
> ----------------------------------------------------------
>
> Key: FLINK-20206
> URL: https://issues.apache.org/jira/browse/FLINK-20206
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / Kubernetes
> Affects Versions: 1.12.0
> Reporter: Guowei Ma
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor, usability
> Attachments: image-2020-11-18-15-12-13-530.png
>
>
> Use ./bin/kubernetes-session.sh to start a k8s session cluster. The log
> showes the session cluster successfully start but it not.
> Personally I prefer the yarn-session way, which could make me have a clear
> expectation.
> So I would like to propose that Flink could give more detail information
> about whether session cluster create success or not.
> !image-2020-11-18-15-12-13-530.png!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
