Rohith commented on YARN-3151:

bq. Any reason why we need to change the test code ?
This is because on CONTAINER_FINISHED event diagnosis message get updated i.e 
proxiedTrackingUrl at final_saving state. And later at failed state, 
proxiedTrackingUrl is assigned with RM Home page.  In test , diagnosis message 
is verified with keyword {{proxy}}. After patch, proxiedTrackingUrl is updated 
with RMHome page at final_saving state. So, test is changed accordingly. I 
believe, it was a bug previously which was pointing to url which can not be 

> On Failover tracking url wrong in application cli for KILLED application
> ------------------------------------------------------------------------
>                 Key: YARN-3151
>                 URL: https://issues.apache.org/jira/browse/YARN-3151
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: client, resourcemanager
>    Affects Versions: 2.6.0
>         Environment: 2 RM HA 
>            Reporter: Bibin A Chundatt
>            Assignee: Rohith
>            Priority: Minor
>         Attachments: 0001-YARN-3151.patch, 0002-YARN-3151.patch, 
> 0002-YARN-3151.patch
> Run an application and kill the same after starting
> Check {color:red} ./yarn application -list -appStates KILLED {color}
> (empty line)
> {quote}
>                 Application-Id Tracking-URL
> application_1423219262738_0001  
> http://<IP>:PORT>/cluster/app/application_1423219262738_0001
> {quote}
> Shutdown the active RM1
> Check the same command {color:red} ./yarn application -list -appStates KILLED 
> {color} after RM2 is active
> {quote}
>                 Application-Id Tracking-URL
> application_1423219262738_0001  null
> {quote}
> Tracking url for application is shown as null 
> Expected : Same url before failover should be shown
> ApplicationReport .getOriginalTrackingUrl() is null after failover
> org.apache.hadoop.yarn.client.cli.ApplicationCLI
> listApplications(Set<String> appTypes,
>       EnumSet<YarnApplicationState> appStates)

This message was sent by Atlassian JIRA

Reply via email to