Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-dev@hadoop.apache.org
Date: Tue, 17 Nov 2015 07:49:10 +0000 (UTC)
From: "Tao Jie (JIRA)" <jira@apache.org>
To: yarn-dev@hadoop.apache.org
Message-ID: <JIRA.12913576.1447746494000.90440.1447746550988@Atlassian.JIRA>
In-Reply-To: <JIRA.12913576.1447746494000@Atlassian.JIRA>
References: <JIRA.12913576.1447746494000@Atlassian.JIRA>
 <JIRA.12913576.1447746494535@arcas>
Subject: [jira] [Created] (YARN-4363) In TestFairScheduler, testcase should
 not create FairScheduler redundantly
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Tao Jie created YARN-4363:
-----------------------------

             Summary: In TestFairScheduler, testcase should not create FairScheduler redundantly
                 Key: YARN-4363
                 URL: https://issues.apache.org/jira/browse/YARN-4363
             Project: Hadoop YARN
          Issue Type: Test
          Components: fairscheduler
    Affects Versions: 2.6.0
            Reporter: Tao Jie
            Priority: Trivial


I am trying to make some improvement on fairscheduler, but get some test failure on TestFairScheduler, due to redundant FairScheduler creation:
In TestFairScheduler, FairScheduler and RM is created, then set RMContext of RM to scheduler.
{code}
@Before
  public void setUp() throws IOException {
    scheduler = new FairScheduler();
    conf = createConfiguration();
    resourceManager = new MockRM(conf);
    scheduler.setRMContext(resourceManager.getRMContext());
  }
{code}
However in several case, scheduler is renewed, as a result RMcontext in scheduler is null.
{code}
 @Test  
  public void testMinZeroResourcesSettings() throws IOException {  
    scheduler = new FairScheduler();
    YarnConfiguration conf = new YarnConfiguration();
    ...
    scheduler.init(conf);
{code}
Then do scheduler.init(conf), I get a NPE(I try to get something from RMContext in scheduler initialization).
So FairScheduler should not be renewed in test block.


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