[jira] [Assigned] (FLINK-9496) Job created time is reset after restart

2019-07-08 Thread vinoyang (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLINK-9496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

vinoyang reassigned FLINK-9496:
---

Assignee: (was: vinoyang)

> Job created time is reset after restart
> ---
>
> Key: FLINK-9496
> URL: https://issues.apache.org/jira/browse/FLINK-9496
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / Metrics
>Affects Versions: 1.2.1, 1.4.0, 1.5.0
>Reporter: Abhinav Bajaj
>Priority: Minor
>
> It seems the "start-time" reported by monitoring API under joboverview ++ is 
> reset after a restart.
> Also, it seems the "start-time" & "timestamps" under job details are also 
> reset when a job is restarted. I expected the "CREATED" date under 
> "timestamps" to be initial created time of the job but it is reset after a 
> job is restarted.
> Probably good to check if the metrics stored in history server has the same 
> issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (FLINK-9496) Job created time is reset after restart

2018-06-02 Thread vinoyang (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLINK-9496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

vinoyang reassigned FLINK-9496:
---

Assignee: vinoyang

> Job created time is reset after restart
> ---
>
> Key: FLINK-9496
> URL: https://issues.apache.org/jira/browse/FLINK-9496
> Project: Flink
>  Issue Type: Bug
>  Components: Metrics
>Affects Versions: 1.2.1, 1.4.0, 1.5.0
>Reporter: Abhinav Bajaj
>Assignee: vinoyang
>Priority: Minor
>
> It seems the "start-time" reported by monitoring API under joboverview ++ is 
> reset after a restart.
> Also, it seems the "start-time" & "timestamps" under job details are also 
> reset when a job is restarted. I expected the "CREATED" date under 
> "timestamps" to be initial created time of the job but it is reset after a 
> job is restarted.
> Probably good to check if the metrics stored in history server has the same 
> issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)