You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Pragya Mittal (JIRA)" <ji...@apache.org> on 2016/01/29 11:34:39 UTC
[jira] [Updated] (FALCON-1794) Running API shows instance time in
format 2016-01-29T09:37:00.000Z instead of 2016-01-29T09:37Z
[ https://issues.apache.org/jira/browse/FALCON-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pragya Mittal updated FALCON-1794:
----------------------------------
Description:
Running api shows following result for native scheduler
{format}
dataqa@lda01:~$ falcon instance -type process -name processMerlinNative -running
Consolidated Status: SUCCEEDED
Instances:
Instance Cluster SourceCluster Status Start End Details Log
-----------------------------------------------------------------------------------------------
2016-01-29T09:37:00.000Z ProcessMultipleClustersTest-corp-ed7e77d1 - RUNNING 2016-01-29T10:27Z -- -
2016-01-29T09:38:00.000Z ProcessMultipleClustersTest-corp-ed7e77d1 - RUNNING 2016-01-29T10:27Z -- -
2016-01-29T09:37:00.000Z ProcessMultipleClustersTest-corp-f62f3b66 - RUNNING 2016-01-29T10:27Z -- -
2016-01-29T09:38:00.000Z ProcessMultipleClustersTest-corp-f62f3b66 - RUNNING 2016-01-29T10:27Z -- -
{format}
While oozie scheduled process shows following result
{format}
dataqa@lda01:~$ falcon instance -type process -name processMerlinOozie -running
Consolidated Status: SUCCEEDED
Instances:
Instance Cluster SourceCluster Status Start End Details Log
-----------------------------------------------------------------------------------------------
2016-01-29T09:40Z ProcessMultipleClustersTest-corp-ed7e77d1 - RUNNING 2016-01-29T10:28Z - --
2016-01-29T09:39Z ProcessMultipleClustersTest-corp-ed7e77d1 - RUNNING 2016-01-29T10:28Z - --
2016-01-29T09:38Z ProcessMultipleClustersTest-corp-f62f3b66 - RUNNING 2016-01-29T10:27Z - --
2016-01-29T09:37Z ProcessMultipleClustersTest-corp-f62f3b66 - RUNNING 2016-01-29T10:27Z - --
{format}
There are two concerns :
1. Instance time format :
Native - 2016-01-29T09:37:00.000Z
Oozie - 2016-01-29T09:40Z
2. Order of instances -
Native - Ascending
Oozie - Descending
> Running API shows instance time in format 2016-01-29T09:37:00.000Z instead of 2016-01-29T09:37Z
> -----------------------------------------------------------------------------------------------
>
> Key: FALCON-1794
> URL: https://issues.apache.org/jira/browse/FALCON-1794
> Project: Falcon
> Issue Type: Improvement
> Components: scheduler
> Affects Versions: 0.9
> Reporter: Pragya Mittal
>
> Running api shows following result for native scheduler
> {format}
> dataqa@lda01:~$ falcon instance -type process -name processMerlinNative -running
> Consolidated Status: SUCCEEDED
> Instances:
> Instance Cluster SourceCluster Status Start End Details Log
> -----------------------------------------------------------------------------------------------
> 2016-01-29T09:37:00.000Z ProcessMultipleClustersTest-corp-ed7e77d1 - RUNNING 2016-01-29T10:27Z -- -
> 2016-01-29T09:38:00.000Z ProcessMultipleClustersTest-corp-ed7e77d1 - RUNNING 2016-01-29T10:27Z -- -
> 2016-01-29T09:37:00.000Z ProcessMultipleClustersTest-corp-f62f3b66 - RUNNING 2016-01-29T10:27Z -- -
> 2016-01-29T09:38:00.000Z ProcessMultipleClustersTest-corp-f62f3b66 - RUNNING 2016-01-29T10:27Z -- -
> {format}
> While oozie scheduled process shows following result
> {format}
> dataqa@lda01:~$ falcon instance -type process -name processMerlinOozie -running
> Consolidated Status: SUCCEEDED
> Instances:
> Instance Cluster SourceCluster Status Start End Details Log
> -----------------------------------------------------------------------------------------------
> 2016-01-29T09:40Z ProcessMultipleClustersTest-corp-ed7e77d1 - RUNNING 2016-01-29T10:28Z - --
> 2016-01-29T09:39Z ProcessMultipleClustersTest-corp-ed7e77d1 - RUNNING 2016-01-29T10:28Z - --
> 2016-01-29T09:38Z ProcessMultipleClustersTest-corp-f62f3b66 - RUNNING 2016-01-29T10:27Z - --
> 2016-01-29T09:37Z ProcessMultipleClustersTest-corp-f62f3b66 - RUNNING 2016-01-29T10:27Z - --
> {format}
> There are two concerns :
> 1. Instance time format :
> Native - 2016-01-29T09:37:00.000Z
> Oozie - 2016-01-29T09:40Z
> 2. Order of instances -
> Native - Ascending
> Oozie - Descending
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)