[
https://issues.apache.org/jira/browse/FLINK-16867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17164519#comment-17164519
]
Steven Zhen Wu commented on FLINK-16867:
----------------------------------------
I should clarify that web.timeout becomes irrelevant to us for job submission
via REST API. It seems that only client.timeout matters for that particular
code path of submitting job.
> Simplify default timeout configuration
> --------------------------------------
>
> Key: FLINK-16867
> URL: https://issues.apache.org/jira/browse/FLINK-16867
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Configuration, Runtime / Coordination
> Affects Versions: 1.9.2, 1.10.0, 1.11.0
> Reporter: Till Rohrmann
> Priority: Minor
> Fix For: 1.12.0
>
>
> At the moment, Flink has several timeout options:
> * {{akka.ask.timeout}}: Timeout for intra cluster RPCs (JM <\-> RM <\-> TE)
> * {{web.timeout}}: Timeout for RPCs between REST handlers and RM, JM, TE
> At the moment, these values are separately configured. This requires the user
> to know about both configuration options and that Flink has multiple timeout
> values.
> In order to simplify setups I would suggest that {{web.timeout}} defaults to
> {{akka.ask.timeout}}, if {{web.timeout}} has not been explicitly configured.
> This has the benefits that the user only need to know about a single timeout
> value which is applied cluster wide.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
