You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "sandflee (JIRA)" <ji...@apache.org> on 2015/04/26 01:39:38 UTC

[jira] [Created] (YARN-3546) AbstractYarnScheduler.getApplicationAttempt seems misleading, and there're some misuse of it

sandflee created YARN-3546:
------------------------------

             Summary: AbstractYarnScheduler.getApplicationAttempt seems misleading,  and there're some misuse of it
                 Key: YARN-3546
                 URL: https://issues.apache.org/jira/browse/YARN-3546
             Project: Hadoop YARN
          Issue Type: Bug
          Components: resourcemanager
            Reporter: sandflee


I'm not familiar with scheduler,  with first eyes, I thought this func returns the schdulerAppAttempt info corresponding to appAttemptId, but actually it returns the current schdulerAppAttempt.
It seems misled others too, such as
TestWorkPreservingRMRestart.waitForNumContainersToRecover
MockRM.waitForSchedulerAppAttemptAdded
should I rename it to T getCurrentSchedulerApplicationAttempt(ApplicationId applicationid)
or returns null  if current attempt id not equals to the request attempt id ?
comment preferred!



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