[
https://issues.apache.org/jira/browse/FLINK-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15604971#comment-15604971
]
Philipp von dem Bussche edited comment on FLINK-4888 at 10/25/16 10:57 AM:
---------------------------------------------------------------------------
[~Zentol] thanks for that. There is a map currentJobs which is used to get the
running jobs and their status. What if we introduce something similar for the
archived jobs and their status in order to avoid those repeated RPC calls ? I
could have a look at where we could populate the map.
was (Author: philipp.bussche):
[~Zentol] thanks for that. There is a map currentJobs which is used to get the
running jobs. What if we introduce something similar for the archived jobs and
their status in order to avoid those repeated RPC calls ? I could have a look
at where we could populate the map.
> instantiated job manager metrics missing important job statistics
> ------------------------------------------------------------------
>
> Key: FLINK-4888
> URL: https://issues.apache.org/jira/browse/FLINK-4888
> Project: Flink
> Issue Type: Improvement
> Components: Metrics
> Affects Versions: 1.1.2
> Reporter: Philipp von dem Bussche
> Assignee: Philipp von dem Bussche
> Priority: Minor
>
> A jobmanager is currently (only) instantiated with the following metrics:
> taskSlotsAvailable, taskSlotsTotal, numRegisteredTaskManagers and
> numRunningJobs. Important other metrics would be numFailedJobs,
> numCancelledJobs and numFinishedJobs. Also to get parity between JobManager
> metrics and whats available via the REST API it would be good to have these.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
