You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/09/03 20:53:00 UTC
[jira] [Commented] (FLINK-7409) WebRuntimeMonitor blocks serving
threads
[ https://issues.apache.org/jira/browse/FLINK-7409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16151946#comment-16151946 ]
ASF GitHub Bot commented on FLINK-7409:
---------------------------------------
Github user tillrohrmann commented on the issue:
https://github.com/apache/flink/pull/4527
Failing test cases are unrelated. Merging this PR.
> WebRuntimeMonitor blocks serving threads
> ----------------------------------------
>
> Key: FLINK-7409
> URL: https://issues.apache.org/jira/browse/FLINK-7409
> Project: Flink
> Issue Type: Improvement
> Components: Webfrontend
> Affects Versions: 1.4.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Minor
>
> The {{WebRuntimeMonitor}} contains a lot of blocking operations where it retrieves a result from the {{JobManager}} and then waits on the future to obtain the result. This is not a good design since we are blocking server threads with that. Instead I propose to follow a more reactive approach where the {{RequestHandler}} returns a {{CompletableFuture}} of {{FullHttpResonse}} which is in the completion handler written out to the channel.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)