You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Pallavi Rao (JIRA)" <ji...@apache.org> on 2016/01/11 05:34:39 UTC

[jira] [Commented] (FALCON-1740) Killed API response in case of succeeded instances

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

Pallavi Rao commented on FALCON-1740:
-------------------------------------

With Native scheduler, it is showing that no instances were KILLED. We can change it to show instances that have SUCCEEDED to make it compatible. But, I think the response with Oozie scheduler is a little confusing. When I looked at it I thought status SUCCEEDED meant KILL was SUCCESSFUL.

> Killed API response in case of succeeded instances
> --------------------------------------------------
>
>                 Key: FALCON-1740
>                 URL: https://issues.apache.org/jira/browse/FALCON-1740
>             Project: Falcon
>          Issue Type: Sub-task
>          Components: oozie, scheduler
>    Affects Versions: 0.9
>            Reporter: Pragya Mittal
>
> In case of succeeded instances , killed API has different behaviour based on the scheduler choice.
> For oozie :
> {noformat}
> dataqa@lda01:~$ fipkill processMerlinOozie -start 2016-01-08T12:13Z -end 2016-01-08T12:15Z
> Consolidated Status: SUCCEEDED
> Instances:
> Instance		Cluster		SourceCluster		Status		Start		End		Details					Log
> -----------------------------------------------------------------------------------------------
> 2016-01-08T12:13Z	ProcessMultipleClustersTest-corp-9706f068	-	SUCCEEDED	2016-01-08T12:13Z	2016-01-08T12:13Z	-	http://8RPCG32.corp.inmobi.com:11000/oozie?job=0001811-160104160825636-oozie-oozi-W
> 2016-01-08T12:13Z	ProcessMultipleClustersTest-corp-0b270a1d	-	SUCCEEDED	2016-01-08T12:13Z	2016-01-08T12:13Z	-	http://lda01:11000/oozie?job=0002247-160104115615658-oozie-oozi-W
> Additional Information:
> Response: ua1/KILL
> ua2/KILL
> Request Id: ua1/871377866@qtp-630572412-35 - 2a1fdd50-dfa3-40a0-8349-5dd8c28be2ff
> ua2/1554129706@qtp-536122141-13 - fff688ea-b65d-4b85-a615-86f7f5989643
> {noformat}
> For native :
> {noformat}
> dataqa@lda01:~$ fipkill ProcessMultipleClustersTest-agregator-coord16-8f55f59b -start 2016-01-08T12:13Z -end 2016-01-08T12:15Z
> Consolidated Status: SUCCEEDED
> Instances:
> Instance		Cluster		SourceCluster		Status		Start		End		Details					Log
> -----------------------------------------------------------------------------------------------
> Additional Information:
> Response: ua1/KILL
> ua2/KILL
> Request Id: ua1/871377866@qtp-630572412-35 - 45e13594-f203-40df-be3a-acb1beb13c52
> ua2/1554129706@qtp-536122141-13 - a6703c0a-968e-4089-83dc-c34ad8460634
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)