[
https://issues.apache.org/jira/browse/FLINK-8949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16984281#comment-16984281
]
lining commented on FLINK-8949:
-------------------------------
This solution could solve the problem of watermarks. However, if users want to
get the other metrics for the subtasks under the vertex, they will encounter
the same problem.
Maybe we need a more generic solution for this situation, such as querying
metrics based on the subtask id range(start subtask id and end subtask id)
other than the specific subtask id.
For example, the user wants to get the current LowWatermark of vertices which
parallelism is 100, URL is
/jobs/:jobid/vertices/:vertexId/metrics?get=currentLowWatermark & subtaskStart
= 0 & subtaskEnd = 99. Other metrics, they just change the value of get.
> Rest API failure with long URL
> ------------------------------
>
> Key: FLINK-8949
> URL: https://issues.apache.org/jira/browse/FLINK-8949
> Project: Flink
> Issue Type: Bug
> Components: Runtime / REST, Runtime / Web Frontend
> Affects Versions: 1.4.2, 1.5.0, 1.6.4, 1.7.2, 1.8.2
> Reporter: Truong Duc Kien
> Assignee: Maximilian Michels
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When you have jobs with high parallelism, the URL for a REST request can get
> very long. When the URL is longer than 4096 bytes, the REST API will return
> error
> {{Failure: 404 Not Found}}
> This can easily be seen in the Web UI, when Flink queries for the watermark
> using the REST API:
> {{GET
> /jobs/:jobId/vertices/:vertexId/metrics?get=0.currentLowWatermark,1.currentLowWatermark,2.currentLo...}}
> The request will fail with more than 170 subtasks and the watermark will not
> be displayed in the Web UI.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
