[
https://issues.apache.org/jira/browse/FLINK-38956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yuepeng Pan updated FLINK-38956:
--------------------------------
Description:
h1. Issues if the design candidate accepted
After applying the fix（FLINK-33123） based on the current approach, there is
still an issue with the Web UI when displaying edge types during a rescale.
Specifically, after a job is rescaled, the page needs to be manually refreshed
before the correct edge types are shown in a timely manner, as illustrated in
[here|https://docs.google.com/document/d/1e_6o4bdXcKtFL3xYxKeyKnRjR8ffsw6Z8frp3tp7u-M/edit?tab=t.0#heading=h.hxuucagvlvbj]
or following:
!image-2026-01-21-21-24-45-096.png!
h2. The root cause
The UI used the job graph edges cache and did not use the latest edge name to
show.
h2. The Solution
It is sufficient to remove the caching mechanism for JobGraph edges in the
corresponding frontend page request logic and instead use the latest retrieved
edge information(from [http://$|http://$/]
{host}
:${port}/jobs/${jobid}).
was:
h1. Issues if the design candidate accepted
After applying the fix（FLINK-33123） based on the current approach, there is
still an issue with the Web UI when displaying edge types during a rescale.
Specifically, after a job is rescaled, the page needs to be manually refreshed
before the correct edge types are shown in a timely manner, as illustrated in
[here|https://docs.google.com/document/d/1e_6o4bdXcKtFL3xYxKeyKnRjR8ffsw6Z8frp3tp7u-M/edit?tab=t.0#heading=h.49ri1jpfilzl]
h2. The root cause
The UI used the job graph edges cache and did not use the latest edge name to
show.
h2. The Solution
It is sufficient to remove the caching mechanism for JobGraph edges in the
corresponding frontend page request logic and instead use the latest retrieved
edge information(from [http://$|http://$/]{host}:${port}/jobs/${jobid}).
> The Web UI cannot automatically show the latest edge name for
> AdaptiveScheduler
> -------------------------------------------------------------------------------
>
> Key: FLINK-38956
> URL: https://issues.apache.org/jira/browse/FLINK-38956
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Web Frontend
> Affects Versions: 2.2.0
> Reporter: Yuepeng Pan
> Priority: Minor
> Attachments: image-2026-01-21-21-24-45-096.png
>
>
> h1. Issues if the design candidate accepted
> After applying the fix（FLINK-33123） based on the current approach, there is
> still an issue with the Web UI when displaying edge types during a rescale.
> Specifically, after a job is rescaled, the page needs to be manually
> refreshed before the correct edge types are shown in a timely manner, as
> illustrated in
> [here|https://docs.google.com/document/d/1e_6o4bdXcKtFL3xYxKeyKnRjR8ffsw6Z8frp3tp7u-M/edit?tab=t.0#heading=h.hxuucagvlvbj]
> or following:
> !image-2026-01-21-21-24-45-096.png!
>
> h2. The root cause
> The UI used the job graph edges cache and did not use the latest edge name to
> show.
> h2. The Solution
> It is sufficient to remove the caching mechanism for JobGraph edges in the
> corresponding frontend page request logic and instead use the latest
> retrieved edge information(from [http://$|http://$/]
> {host}
> :${port}/jobs/${jobid}).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
