[
https://issues.apache.org/jira/browse/FLINK-14470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16955720#comment-16955720
]
Yadong Xie commented on FLINK-14470:
------------------------------------
[~wind_ljy]
We could do something like that, but I think the 4000 limited is a magic
number, which may not a very good idea in system design.
There are also many REST API meet the same problem, like the subtask list which
also will almost sure to break when the parallelism is too high.
> Watermark display not working with high parallelism job
> -------------------------------------------------------
>
> Key: FLINK-14470
> URL: https://issues.apache.org/jira/browse/FLINK-14470
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Web Frontend
> Affects Versions: 1.8.2, 1.9.1
> Reporter: Thomas Weise
> Assignee: Yadong Xie
> Priority: Major
>
> Watermarks don't display in the UI when the job graph has many vertices. The
> REST API call to fetch currentInputWatermark fails as it enumerates each
> subtask, which obviously fails beyond a limit. With the new UI that can be
> noticed through a flickering error message in the upper right corner.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
