[ 
https://issues.apache.org/jira/browse/FLINK-14470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16984181#comment-16984181
 ] 

lining edited comment on FLINK-14470 at 11/28/19 7:28 AM:
----------------------------------------------------------

I have tested it if you get more than 165 WaterMarks, will redirect to URL 
/bad-request. There isn't any handler for it, so its Http status is 404. Find 
someone who has asked a similar 
[question|https://groups.google.com/forum/#!topic/gatling/9LtKV5sSXxU] in 
GoogleGroup. The 
[doc|https://netty.io/4.0/api/io/netty/handler/codec/http/HttpRequestDecoder.html]
 for maxInitialLineLength and its default value is 4096 in [code.  
|https://github.com/netty/netty/blob/4.1/codec-http/src/main/java/io/netty/handler/codec/http/HttpRequestDecoder.java#L59]
 * the reason for redirecting to /bad-request is the URL exceeds 4kb. In 
HttpRequestDecoder, if it decodes invalid will redirect to /bad-request.
 * if Http call has an exception, it needs to show the error, not redirect to 
/bad-request.
 * new handler for getting vertex's metric, such as 
/jobs/:jobid/vertices/:vertexId/metrics?get=[key]&subtaskStart=[]&subtaskEnd=[]


was (Author: lining):
I have tested it if you get more than 165 WaterMarks, will redirect to URL 
/bad-request. There isn't any handler for it, so its Http status is 404. Find 
someone who has asked a similar 
[question|https://groups.google.com/forum/#!topic/gatling/9LtKV5sSXxU] in 
GoogleGroup. The 
[doc|https://netty.io/4.0/api/io/netty/handler/codec/http/HttpRequestDecoder.html]
 for maxInitialLineLength and its default value is 4096 in 
[code.|https://github.com/netty/netty/blob/4.1/codec-http/src/main/java/io/netty/handler/codec/http/HttpRequestDecoder.java#L59]
 * the reason for redirecting to /bad-request is the URL exceeds 4kb. 
 * if Http call has an exception, it needs to show the error, not redirect to 
/bad-request.
 * new handler for getting vertex's metric, such as 
/jobs/:jobid/vertices/:vertexId/metrics?get=[key]&subtaskStart=[]&subtaskEnd=[]

> 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)

Reply via email to