Hadoop YARN
  1. Hadoop YARN
  2. YARN-357

App submission should not be synchronized

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.23.3, 3.0.0, 2.0.0-alpha
    • Fix Version/s: 2.0.3-alpha, 0.23.7
    • Component/s: resourcemanager
    • Labels:
      None

      Description

      MAPREDUCE-2953 fixed a race condition with querying of app status by making RMClientService#submitApplication synchronously invoke RMAppManager#submitApplication. However, the synchronized keyword was also added to RMAppManager#submitApplication with the comment:

      I made the submitApplication synchronized to keep it consistent with the other routines in RMAppManager although I do not believe it needs it since the rmapp datastructure is already a concurrentMap and I don't see anything else that would be an issue.

      It's been observed that app submission latency is being unnecessarily impacted.

      1. YARN-357.txt
        8 kB
        Siddharth Seth
      2. YARN-357.patch
        0.9 kB
        Daryn Sharp
      3. YARN-357.patch
        8 kB
        Daryn Sharp
      4. YARN-357.branch-23.patch
        8 kB
        Daryn Sharp

        Issue Links

          Activity

          Hide
          Daryn Sharp added a comment -

          Existing tests for MAPREDUCE-2953 demonstrate the race is fixed w/o synchronizing the method.

          Show
          Daryn Sharp added a comment - Existing tests for MAPREDUCE-2953 demonstrate the race is fixed w/o synchronizing the method.
          Hide
          Daryn Sharp added a comment -

          Tom is on vacation, but I remember the internal debate if it should be synchronized. It was only added as a defensive measure.

          Show
          Daryn Sharp added a comment - Tom is on vacation, but I remember the internal debate if it should be synchronized. It was only added as a defensive measure.
          Hide
          Hadoop QA added a comment -

          -1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12566348/YARN-357.patch
          against trunk revision .

          +1 @author. The patch does not contain any @author tags.

          -1 tests included. The patch doesn't appear to include any new or modified tests.
          Please justify why no new tests are needed for this patch.
          Also please list what manual steps were performed to verify this patch.

          +1 javac. The applied patch does not increase the total number of javac compiler warnings.

          +1 javadoc. The javadoc tool did not generate any warning messages.

          -1 eclipse:eclipse. The patch failed to build with eclipse:eclipse.

          +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.

          +1 release audit. The applied patch does not increase the total number of release audit warnings.

          +1 core tests. The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.

          +1 contrib tests. The patch passed contrib unit tests.

          Test results: https://builds.apache.org/job/PreCommit-YARN-Build/364//testReport/
          Console output: https://builds.apache.org/job/PreCommit-YARN-Build/364//console

          This message is automatically generated.

          Show
          Hadoop QA added a comment - -1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12566348/YARN-357.patch against trunk revision . +1 @author . The patch does not contain any @author tags. -1 tests included . The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . The javadoc tool did not generate any warning messages. -1 eclipse:eclipse . The patch failed to build with eclipse:eclipse. +1 findbugs . The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit . The applied patch does not increase the total number of release audit warnings. +1 core tests . The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager. +1 contrib tests . The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-YARN-Build/364//testReport/ Console output: https://builds.apache.org/job/PreCommit-YARN-Build/364//console This message is automatically generated.
          Hide
          Jason Lowe added a comment -

          If we can safely remove the synchronization, it sounds good. However it looks like DelegationTokenRenewer#addApplication is another chokepoint right behind RMAppManager#submitApplication, so fixing just the former probably won't help in practice without fixing that as well.

          Show
          Jason Lowe added a comment - If we can safely remove the synchronization, it sounds good. However it looks like DelegationTokenRenewer#addApplication is another chokepoint right behind RMAppManager#submitApplication , so fixing just the former probably won't help in practice without fixing that as well.
          Hide
          Daryn Sharp added a comment -

          Add tests that both better verify MAPREDUCE-2953 by ensuring ClientRMService is synchronously calling RMAppManager, but that RMAppManager is not synchronizing concurrent job submissions.

          Show
          Daryn Sharp added a comment - Add tests that both better verify MAPREDUCE-2953 by ensuring ClientRMService is synchronously calling RMAppManager , but that RMAppManager is not synchronizing concurrent job submissions.
          Hide
          Hadoop QA added a comment -

          -1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12566815/YARN-357.patch
          against trunk revision .

          +1 @author. The patch does not contain any @author tags.

          +1 tests included. The patch appears to include 1 new or modified test files.

          +1 javac. The applied patch does not increase the total number of javac compiler warnings.

          +1 javadoc. The javadoc tool did not generate any warning messages.

          +1 eclipse:eclipse. The patch built with eclipse:eclipse.

          +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.

          +1 release audit. The applied patch does not increase the total number of release audit warnings.

          -1 core tests. The patch failed these unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:

          org.apache.hadoop.yarn.server.resourcemanager.webapp.TestRMWebServices

          +1 contrib tests. The patch passed contrib unit tests.

          Test results: https://builds.apache.org/job/PreCommit-YARN-Build/373//testReport/
          Console output: https://builds.apache.org/job/PreCommit-YARN-Build/373//console

          This message is automatically generated.

          Show
          Hadoop QA added a comment - -1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12566815/YARN-357.patch against trunk revision . +1 @author . The patch does not contain any @author tags. +1 tests included . The patch appears to include 1 new or modified test files. +1 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . The javadoc tool did not generate any warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. +1 findbugs . The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit . The applied patch does not increase the total number of release audit warnings. -1 core tests . The patch failed these unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager: org.apache.hadoop.yarn.server.resourcemanager.webapp.TestRMWebServices +1 contrib tests . The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-YARN-Build/373//testReport/ Console output: https://builds.apache.org/job/PreCommit-YARN-Build/373//console This message is automatically generated.
          Hide
          Jason Lowe added a comment -

          TestRMWebServices failure is likely unrelated, see HADOOP-9246.

          Show
          Jason Lowe added a comment - TestRMWebServices failure is likely unrelated, see HADOOP-9246 .
          Hide
          Daryn Sharp added a comment -

          Yes, the test failed on a non-patched trunk build.

          Show
          Daryn Sharp added a comment - Yes, the test failed on a non-patched trunk build.
          Hide
          Siddharth Seth added a comment -

          Couldn't see any reason for submitApplication to be synchronized, so this looks good.

          Minor nits in the unit test.

          • An assert within a thread will not cause the test to fail. The test works however, since it'll time out. Having an explicit error may be better.
          • The test ends up relying on Mockito handling multiple threads - and resetting a mock mid way through an invocation. Was playing with this - mockito seemed to be serializing invocations to the mock. So the second submit would hang, without the reset. Chaining is supposed to work via - doAnswer().doNothing.when().... Think it may be better to write a custom eventHandler for this test.

          There's a bunch of other synchronized methods in RMAppManager, which could likely be cleaned up. Will open a separate jira to track this.

          Show
          Siddharth Seth added a comment - Couldn't see any reason for submitApplication to be synchronized, so this looks good. Minor nits in the unit test. An assert within a thread will not cause the test to fail. The test works however, since it'll time out. Having an explicit error may be better. The test ends up relying on Mockito handling multiple threads - and resetting a mock mid way through an invocation. Was playing with this - mockito seemed to be serializing invocations to the mock. So the second submit would hang, without the reset. Chaining is supposed to work via - doAnswer().doNothing.when().... Think it may be better to write a custom eventHandler for this test. There's a bunch of other synchronized methods in RMAppManager, which could likely be cleaned up. Will open a separate jira to track this.
          Hide
          Daryn Sharp added a comment -

          Thanks for the review! I struggled quite a bit with writing these tests. I am indeed expecting the barrier to cause the test to timeout. How do you suggest I add an explicit error? Log the assert since there's not much else I can (easily) do?

          I couldn't get chaining to work with void return methods. The mock hangs on a poll for repeated calls to a method with a doAnswer if there aren't more doAnswers registered with it, but since I couldn't get the chaining to work up-front, I added the chain after the method is hit the first time.

          How would a custom event handler work better in this case? I think it'd just mimic the current behavior? Could we maybe have the separate jira, for removing other syncs, improve the tests in general? Or could you help me out by updating the tests since I'm unclear what to do?

          Show
          Daryn Sharp added a comment - Thanks for the review! I struggled quite a bit with writing these tests. I am indeed expecting the barrier to cause the test to timeout. How do you suggest I add an explicit error? Log the assert since there's not much else I can (easily) do? I couldn't get chaining to work with void return methods. The mock hangs on a poll for repeated calls to a method with a doAnswer if there aren't more doAnswers registered with it, but since I couldn't get the chaining to work up-front, I added the chain after the method is hit the first time. How would a custom event handler work better in this case? I think it'd just mimic the current behavior? Could we maybe have the separate jira, for removing other syncs, improve the tests in general? Or could you help me out by updating the tests since I'm unclear what to do?
          Hide
          Siddharth Seth added a comment -

          Thanks for the review! I struggled quite a bit with writing these tests. I am indeed expecting the barrier to cause the test to timeout. How do you suggest I add an explicit error? Log the assert since there's not much else I can (easily) do?

          A flag to track the error in the thread should work ?

          I couldn't get chaining to work with void return methods. The mock hangs on a poll for repeated calls to a method with a doAnswer if there aren't more doAnswers registered with it, but since I couldn't get the chaining to work up-front, I added the chain after the method is hit the first time.

          Chaining seemed to work ok, as long as the previous invocation had completed. Even without chaining, the mock does not seem to handle multiple parallel invocations. Struggled a bit with this as well - which is what makes me a little wary of using mockito for this case (http://code.google.com/p/mockito/wiki/FAQ).

          How would a custom event handler work better in this case? I think it'd just mimic the current behavior? Could we maybe have the separate jira, for removing other syncs, improve the tests in general? Or could you help me out by updating the tests since I'm unclear what to do?

          It'd behave the same, except would not use mockito for the EventHandler mock. Sure, I'll try updating the unit test.

          Show
          Siddharth Seth added a comment - Thanks for the review! I struggled quite a bit with writing these tests. I am indeed expecting the barrier to cause the test to timeout. How do you suggest I add an explicit error? Log the assert since there's not much else I can (easily) do? A flag to track the error in the thread should work ? I couldn't get chaining to work with void return methods. The mock hangs on a poll for repeated calls to a method with a doAnswer if there aren't more doAnswers registered with it, but since I couldn't get the chaining to work up-front, I added the chain after the method is hit the first time. Chaining seemed to work ok, as long as the previous invocation had completed. Even without chaining, the mock does not seem to handle multiple parallel invocations. Struggled a bit with this as well - which is what makes me a little wary of using mockito for this case ( http://code.google.com/p/mockito/wiki/FAQ ). How would a custom event handler work better in this case? I think it'd just mimic the current behavior? Could we maybe have the separate jira, for removing other syncs, improve the tests in general? Or could you help me out by updating the tests since I'm unclear what to do? It'd behave the same, except would not use mockito for the EventHandler mock. Sure, I'll try updating the unit test.
          Hide
          Siddharth Seth added a comment -

          Pretty much the same patch, but with the mockito EventHandler replaced.
          I'm +1 on the previous patch. Daryn, if you think this change to the unit test looks OK, please go ahead and commit it. Thanks

          Show
          Siddharth Seth added a comment - Pretty much the same patch, but with the mockito EventHandler replaced. I'm +1 on the previous patch. Daryn, if you think this change to the unit test looks OK, please go ahead and commit it. Thanks
          Hide
          Hadoop QA added a comment -

          +1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12568093/YARN-357.txt
          against trunk revision .

          +1 @author. The patch does not contain any @author tags.

          +1 tests included. The patch appears to include 1 new or modified test files.

          +1 javac. The applied patch does not increase the total number of javac compiler warnings.

          +1 javadoc. The javadoc tool did not generate any warning messages.

          +1 eclipse:eclipse. The patch built with eclipse:eclipse.

          +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.

          +1 release audit. The applied patch does not increase the total number of release audit warnings.

          +1 core tests. The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.

          +1 contrib tests. The patch passed contrib unit tests.

          Test results: https://builds.apache.org/job/PreCommit-YARN-Build/382//testReport/
          Console output: https://builds.apache.org/job/PreCommit-YARN-Build/382//console

          This message is automatically generated.

          Show
          Hadoop QA added a comment - +1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12568093/YARN-357.txt against trunk revision . +1 @author . The patch does not contain any @author tags. +1 tests included . The patch appears to include 1 new or modified test files. +1 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . The javadoc tool did not generate any warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. +1 findbugs . The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit . The applied patch does not increase the total number of release audit warnings. +1 core tests . The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager. +1 contrib tests . The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-YARN-Build/382//testReport/ Console output: https://builds.apache.org/job/PreCommit-YARN-Build/382//console This message is automatically generated.
          Hide
          Daryn Sharp added a comment -

          Sid, thanks a lot for your help. I'll commit shortly.

          Show
          Daryn Sharp added a comment - Sid, thanks a lot for your help. I'll commit shortly.
          Hide
          Hudson added a comment -

          Integrated in Hadoop-trunk-Commit #3330 (See https://builds.apache.org/job/Hadoop-trunk-Commit/3330/)
          YARN-357. App submission should not be synchronized (daryn) (Revision 1443016)

          Result = SUCCESS
          daryn : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1443016
          Files :

          • /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
          • /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/RMAppManager.java
          • /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestClientRMService.java
          Show
          Hudson added a comment - Integrated in Hadoop-trunk-Commit #3330 (See https://builds.apache.org/job/Hadoop-trunk-Commit/3330/ ) YARN-357 . App submission should not be synchronized (daryn) (Revision 1443016) Result = SUCCESS daryn : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1443016 Files : /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/RMAppManager.java /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestClientRMService.java
          Hide
          Daryn Sharp added a comment -

          For branch 23, change test to use ApplicationsStore instead of RMStateStore.

          Show
          Daryn Sharp added a comment - For branch 23, change test to use ApplicationsStore instead of RMStateStore .
          Hide
          Hadoop QA added a comment -

          -1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12568245/YARN-357.branch-23.patch
          against trunk revision .

          -1 patch. The patch command could not apply the patch.

          Console output: https://builds.apache.org/job/PreCommit-YARN-Build/384//console

          This message is automatically generated.

          Show
          Hadoop QA added a comment - -1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12568245/YARN-357.branch-23.patch against trunk revision . -1 patch . The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-YARN-Build/384//console This message is automatically generated.
          Hide
          Daryn Sharp added a comment -

          Merged to trunk, branch 2, 2.0.3, and 23.

          Show
          Daryn Sharp added a comment - Merged to trunk, branch 2, 2.0.3, and 23.
          Hide
          Hudson added a comment -

          Integrated in Hadoop-Yarn-trunk #120 (See https://builds.apache.org/job/Hadoop-Yarn-trunk/120/)
          YARN-357. App submission should not be synchronized (daryn) (Revision 1443016)

          Result = FAILURE
          daryn : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1443016
          Files :

          • /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
          • /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/RMAppManager.java
          • /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestClientRMService.java
          Show
          Hudson added a comment - Integrated in Hadoop-Yarn-trunk #120 (See https://builds.apache.org/job/Hadoop-Yarn-trunk/120/ ) YARN-357 . App submission should not be synchronized (daryn) (Revision 1443016) Result = FAILURE daryn : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1443016 Files : /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/RMAppManager.java /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestClientRMService.java
          Hide
          Hudson added a comment -

          Integrated in Hadoop-Hdfs-0.23-Build #518 (See https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/518/)
          YARN-357. App submission should not be synchronized (daryn) (Revision 1443048)

          Result = SUCCESS
          daryn : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1443048
          Files :

          • /hadoop/common/branches/branch-0.23/hadoop-yarn-project/CHANGES.txt
          • /hadoop/common/branches/branch-0.23/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/RMAppManager.java
          • /hadoop/common/branches/branch-0.23/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestClientRMService.java
          Show
          Hudson added a comment - Integrated in Hadoop-Hdfs-0.23-Build #518 (See https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/518/ ) YARN-357 . App submission should not be synchronized (daryn) (Revision 1443048) Result = SUCCESS daryn : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1443048 Files : /hadoop/common/branches/branch-0.23/hadoop-yarn-project/CHANGES.txt /hadoop/common/branches/branch-0.23/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/RMAppManager.java /hadoop/common/branches/branch-0.23/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestClientRMService.java
          Hide
          Hudson added a comment -

          Integrated in Hadoop-Hdfs-trunk #1309 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1309/)
          YARN-357. App submission should not be synchronized (daryn) (Revision 1443016)

          Result = FAILURE
          daryn : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1443016
          Files :

          • /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
          • /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/RMAppManager.java
          • /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestClientRMService.java
          Show
          Hudson added a comment - Integrated in Hadoop-Hdfs-trunk #1309 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1309/ ) YARN-357 . App submission should not be synchronized (daryn) (Revision 1443016) Result = FAILURE daryn : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1443016 Files : /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/RMAppManager.java /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestClientRMService.java
          Hide
          Hudson added a comment -

          Integrated in Hadoop-Mapreduce-trunk #1337 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1337/)
          YARN-357. App submission should not be synchronized (daryn) (Revision 1443016)

          Result = SUCCESS
          daryn : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1443016
          Files :

          • /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
          • /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/RMAppManager.java
          • /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestClientRMService.java
          Show
          Hudson added a comment - Integrated in Hadoop-Mapreduce-trunk #1337 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1337/ ) YARN-357 . App submission should not be synchronized (daryn) (Revision 1443016) Result = SUCCESS daryn : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1443016 Files : /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/RMAppManager.java /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestClientRMService.java

            People

            • Assignee:
              Daryn Sharp
              Reporter:
              Daryn Sharp
            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development