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

Ajay Yadava commented on FALCON-1740:
-------------------------------------

IMO the oozie response is better. It is clearer because it shows the status of 
instance and not the status of action (action status is shown separately in 
consolidated status). Also if all instances are not listed then some users will 
be left wondering why some instances didn't get killed, so in that case also I 
believe Oozie approach is worth following.

> 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)

Reply via email to