[jira] [Updated] (FLINK-10822) Configurable MetricQueryService interval
[
https://issues.apache.org/jira/browse/FLINK-10822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chesnay Schepler updated FLINK-10822:
-
Issue Type: New Feature (was: Improvement)
> Configurable MetricQueryService interval
>
>
> Key: FLINK-10822
> URL: https://issues.apache.org/jira/browse/FLINK-10822
> Project: Flink
> Issue Type: New Feature
> Components: Runtime / Metrics
>Reporter: Chesnay Schepler
>Assignee: Till Rohrmann
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The {{MetricQueryService}} is used for transmitting metrics from TaskManagers
> to the JobManager, in order to expose them via REST and by extension the
> WebUI.
> By default the JM will poll metrics at most every 10 seconds. This has an
> adverse effect on the duration of our end-to-end tests, which for example
> query metrics via the REST API to determine whether the cluster has started.
> If during the first poll no TM is available it will take another 10 second
> for updated information to be available.
> By making this interval configurable we could this reduce the test duration.
> Additionally this could serve as a switch to disable the
> {{MetricQueryService}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FLINK-10822) Configurable MetricQueryService interval
[
https://issues.apache.org/jira/browse/FLINK-10822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-10822:
---
Labels: pull-request-available (was: )
> Configurable MetricQueryService interval
>
>
> Key: FLINK-10822
> URL: https://issues.apache.org/jira/browse/FLINK-10822
> Project: Flink
> Issue Type: Improvement
> Components: Metrics
>Reporter: Chesnay Schepler
>Assignee: Till Rohrmann
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.8.0
>
>
> The {{MetricQueryService}} is used for transmitting metrics from TaskManagers
> to the JobManager, in order to expose them via REST and by extension the
> WebUI.
> By default the JM will poll metrics at most every 10 seconds. This has an
> adverse effect on the duration of our end-to-end tests, which for example
> query metrics via the REST API to determine whether the cluster has started.
> If during the first poll no TM is available it will take another 10 second
> for updated information to be available.
> By making this interval configurable we could this reduce the test duration.
> Additionally this could serve as a switch to disable the
> {{MetricQueryService}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
