You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/02/04 21:33:39 UTC

[jira] [Commented] (FALCON-1794) Behaviour mismatch in running Api when scheduled on native instead of oozie

    [ https://issues.apache.org/jira/browse/FALCON-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132971#comment-15132971 ] 

ASF GitHub Bot commented on FALCON-1794:
----------------------------------------

GitHub user deepakbarr opened a pull request:

    https://github.com/apache/falcon/pull/26

    FALCON-1794:Behaviour mismatch in running Api when scheduled on nativ…

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/deepakbarr/falcon falcon-1794

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/falcon/pull/26.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #26
    
----
commit 44727e506e7328bfeb79c82787ff3510ec6c8cdb
Author: Deepak Kumar Barr <de...@gmail.com>
Date:   2016-02-04T20:30:42Z

    FALCON-1794:Behaviour mismatch in running Api when scheduled on native instead of oozie

----


> Behaviour mismatch in running Api when scheduled on native instead of oozie
> ---------------------------------------------------------------------------
>
>                 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
>            Assignee: Deepak Barr
>
> Running api shows following result for native scheduler 
> {noformat}
> 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	--	-
> {noformat}
> While oozie scheduled process shows following result
> {noformat}
> 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	-	--
> {noformat}
> 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)