[
https://issues.apache.org/jira/browse/FLINK-29125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681848#comment-17681848
]
Xintong Song commented on FLINK-29125:
--------------------------------------
Sorry for joining the discussion late.
I think option1 is probably the easiest. However, I'm not entirely sure it's
always ok to expose the ip & port on UI. E.g., if the user access the web ui
via a proxy, and the jobmanager ip & port are meant to be internal.
I'm overall -1 for option2. We should not expose the internal dispatcher id.
And introducing another random id could be confusing because we can hardly
explain to the users what is the random string being displayed.
For option3, please be aware we already have a `kubernetes.cluster-id` for
native k8s deployments, and a `yarn.application.id` for yarn deployments. If we
are introducing another `flink.cluster-id`, we would need to clarify the
relationship between these concepts. My gut feeling this might be an overkill
for the simple purpose of distinguishing browser tabs.
In addition to which identifier to choose, I think the way we display the
identifier also matter. `Apache Flink Web Dashboard (<id>)` may not be a good
choice, because when there are many tabs in the browser, most likely the user
would only see `Apache Flink Web ...`.
> Placeholder in Apache Flink Web Frontend to display some "tags" to
> distinguish between frontends of different clusters
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-29125
> URL: https://issues.apache.org/jira/browse/FLINK-29125
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Web Frontend
> Reporter: Durga Krovi
> Priority: Major
> Labels: pull-request-available
>
> When there are several Apache Flink clusters running and the corresponding
> Web Frontend is opened in browser tabs, it would be great if these UIs can be
> distinguished in a visible way. Port number in the browser location bar might
> be useful.
> In our use case, we switch among multiple clusters, connect to only one
> cluster at a time and use the same port for forwarding. In such a case, there
> is no visible cue to identify the cluster of the UI being accessed on the
> browser.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
