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

Junping Du commented on YARN-2016:
----------------------------------

[~venkatnrangan], you are right. When similar bug happens, we often suspect the 
logic in client or server but ignore the wire logic. In most cases, we don't 
even have a simple unit test to verify these PBImpls which cause bug get hidden 
easily. Already filed YARN-2051 to address this, it would be great if you want 
to help there. Thanks!

> Yarn getApplicationRequest start time range is not honored
> ----------------------------------------------------------
>
>                 Key: YARN-2016
>                 URL: https://issues.apache.org/jira/browse/YARN-2016
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.4.0
>            Reporter: Venkat Ranganathan
>            Assignee: Junping Du
>             Fix For: 2.4.1
>
>         Attachments: YARN-2016.patch, YarnTest.java
>
>
> When we query for the previous applications by creating an instance of 
> GetApplicationsRequest and setting the start time range and application tag, 
> we see that the start range provided is not honored and all applications with 
> the tag are returned
> Attaching a reproducer.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to