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 "Siddharth Seth (JIRA)" <ji...@apache.org> on 2012/08/31 23:11:07 UTC
[jira] [Created] (YARN-75) RMContainer should handle a RELEASE
event while RUNNING
Siddharth Seth created YARN-75:
----------------------------------
Summary: RMContainer should handle a RELEASE event while RUNNING
Key: YARN-75
URL: https://issues.apache.org/jira/browse/YARN-75
Project: Hadoop YARN
Issue Type: Bug
Affects Versions: 2.1.0-alpha
Reporter: Siddharth Seth
Assignee: Siddharth Seth
An AppMaster can send a container release at any point. Currently this results in an exception, if this is done while the RM considers the container to be RUNNING.
The event not being processed correctly also implies that these containers do not show up in the Completed Container List seen by the AM (AMRMProtocol). MR-3902 depends on this set being complete.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (YARN-75) RMContainer should handle a RELEASE
event while RUNNING
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/YARN-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13464673#comment-13464673 ]
Hudson commented on YARN-75:
----------------------------
Integrated in Hadoop-Hdfs-0.23-Build #387 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/387/])
svn merge -c 1381806,1381807,1381809,1381811 FIXES: YARN-75. Modified ResourceManager's RMContainer to handle a valid RELEASE event at RUNNING state. Contributed by Siddharth Seth. (Revision 1390695)
Result = UNSTABLE
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1390695
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-api/src/main/java/org/apache/hadoop/yarn/api/protocolrecords/AllocateRequest.java
* /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/rmcontainer/RMContainerImpl.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/rmcontainer
* /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/rmcontainer/TestRMContainerImpl.java
> RMContainer should handle a RELEASE event while RUNNING
> -------------------------------------------------------
>
> Key: YARN-75
> URL: https://issues.apache.org/jira/browse/YARN-75
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.0.0-alpha
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Fix For: 2.0.2-alpha, 0.23.4
>
> Attachments: YARN-75_2.txt, YARN-75.txt
>
>
> An AppMaster can send a container release at any point. Currently this results in an exception, if this is done while the RM considers the container to be RUNNING.
> The event not being processed correctly also implies that these containers do not show up in the Completed Container List seen by the AM (AMRMProtocol). MR-3902 depends on this set being complete.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (YARN-75) RMContainer should handle a RELEASE
event while RUNNING
Posted by "Siddharth Seth (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/YARN-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siddharth Seth updated YARN-75:
-------------------------------
Attachment: YARN-75.txt
RMContainer now goes into a KILLED state in this situation. Would COMPLETED be a better state, since we don't really know the reason for the RELEASE. Does it make sense to differentiate between KILLED and COMPLETED in RMContainer (both being final states).
> RMContainer should handle a RELEASE event while RUNNING
> -------------------------------------------------------
>
> Key: YARN-75
> URL: https://issues.apache.org/jira/browse/YARN-75
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.1.0-alpha
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Attachments: YARN-75.txt
>
>
> An AppMaster can send a container release at any point. Currently this results in an exception, if this is done while the RM considers the container to be RUNNING.
> The event not being processed correctly also implies that these containers do not show up in the Completed Container List seen by the AM (AMRMProtocol). MR-3902 depends on this set being complete.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (YARN-75) RMContainer should handle a RELEASE
event while RUNNING
Posted by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/YARN-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449994#comment-13449994 ]
Vinod Kumar Vavilapalli commented on YARN-75:
---------------------------------------------
Looks good, +1. Triggering Jenkins.
> RMContainer should handle a RELEASE event while RUNNING
> -------------------------------------------------------
>
> Key: YARN-75
> URL: https://issues.apache.org/jira/browse/YARN-75
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.1.0-alpha
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Attachments: YARN-75_2.txt, YARN-75.txt
>
>
> An AppMaster can send a container release at any point. Currently this results in an exception, if this is done while the RM considers the container to be RUNNING.
> The event not being processed correctly also implies that these containers do not show up in the Completed Container List seen by the AM (AMRMProtocol). MR-3902 depends on this set being complete.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (YARN-75) RMContainer should handle a RELEASE
event while RUNNING
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/YARN-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450226#comment-13450226 ]
Hudson commented on YARN-75:
----------------------------
Integrated in Hadoop-Common-trunk-Commit #2700 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2700/])
YARN-75. Missing test. Ugh. (Revision 1381811)
YARN-75. Added file missing from previous commit. Bad day with svn. (Revision 1381809)
YARN-75. Removing spurious file from the previous commit. (Revision 1381807)
YARN-75. Modified ResourceManager's RMContainer to handle a valid RELEASE event at RUNNING state. Contributed by Siddharth Seth. (Revision 1381806)
Result = SUCCESS
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1381811
Files :
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/TestRMContainerImpl.java
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1381809
Files :
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/TestRMContainerImpl.java
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1381807
Files :
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/TestRMContainerImpl.java.orig
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1381806
Files :
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/api/protocolrecords/AllocateRequest.java
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/RMContainerImpl.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/rmcontainer
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/TestRMContainerImpl.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/rmcontainer/TestRMContainerImpl.java.orig
> RMContainer should handle a RELEASE event while RUNNING
> -------------------------------------------------------
>
> Key: YARN-75
> URL: https://issues.apache.org/jira/browse/YARN-75
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.1.0-alpha
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Fix For: 2.1.0-alpha
>
> Attachments: YARN-75_2.txt, YARN-75.txt
>
>
> An AppMaster can send a container release at any point. Currently this results in an exception, if this is done while the RM considers the container to be RUNNING.
> The event not being processed correctly also implies that these containers do not show up in the Completed Container List seen by the AM (AMRMProtocol). MR-3902 depends on this set being complete.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (YARN-75) RMContainer should handle a RELEASE
event while RUNNING
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/YARN-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450009#comment-13450009 ]
Hadoop QA commented on YARN-75:
-------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12543904/YARN-75_2.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-api 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/31//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/31//console
This message is automatically generated.
> RMContainer should handle a RELEASE event while RUNNING
> -------------------------------------------------------
>
> Key: YARN-75
> URL: https://issues.apache.org/jira/browse/YARN-75
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.1.0-alpha
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Attachments: YARN-75_2.txt, YARN-75.txt
>
>
> An AppMaster can send a container release at any point. Currently this results in an exception, if this is done while the RM considers the container to be RUNNING.
> The event not being processed correctly also implies that these containers do not show up in the Completed Container List seen by the AM (AMRMProtocol). MR-3902 depends on this set being complete.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (YARN-75) RMContainer should handle a RELEASE
event while RUNNING
Posted by "Mayank Bansal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/YARN-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449157#comment-13449157 ]
Mayank Bansal commented on YARN-75:
-----------------------------------
+1 looks good to me
Thanks,
Mayank
> RMContainer should handle a RELEASE event while RUNNING
> -------------------------------------------------------
>
> Key: YARN-75
> URL: https://issues.apache.org/jira/browse/YARN-75
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.1.0-alpha
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Attachments: YARN-75_2.txt, YARN-75.txt
>
>
> An AppMaster can send a container release at any point. Currently this results in an exception, if this is done while the RM considers the container to be RUNNING.
> The event not being processed correctly also implies that these containers do not show up in the Completed Container List seen by the AM (AMRMProtocol). MR-3902 depends on this set being complete.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (YARN-75) RMContainer should handle a RELEASE
event while RUNNING
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/YARN-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450632#comment-13450632 ]
Hudson commented on YARN-75:
----------------------------
Integrated in Hadoop-Mapreduce-trunk #1189 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1189/])
YARN-75. Missing test. Ugh. (Revision 1381811)
YARN-75. Added file missing from previous commit. Bad day with svn. (Revision 1381809)
YARN-75. Removing spurious file from the previous commit. (Revision 1381807)
YARN-75. Modified ResourceManager's RMContainer to handle a valid RELEASE event at RUNNING state. Contributed by Siddharth Seth. (Revision 1381806)
Result = SUCCESS
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1381811
Files :
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/TestRMContainerImpl.java
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1381809
Files :
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/TestRMContainerImpl.java
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1381807
Files :
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/TestRMContainerImpl.java.orig
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1381806
Files :
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/api/protocolrecords/AllocateRequest.java
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/RMContainerImpl.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/rmcontainer
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/TestRMContainerImpl.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/rmcontainer/TestRMContainerImpl.java.orig
> RMContainer should handle a RELEASE event while RUNNING
> -------------------------------------------------------
>
> Key: YARN-75
> URL: https://issues.apache.org/jira/browse/YARN-75
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.1.0-alpha
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Fix For: 2.1.0-alpha
>
> Attachments: YARN-75_2.txt, YARN-75.txt
>
>
> An AppMaster can send a container release at any point. Currently this results in an exception, if this is done while the RM considers the container to be RUNNING.
> The event not being processed correctly also implies that these containers do not show up in the Completed Container List seen by the AM (AMRMProtocol). MR-3902 depends on this set being complete.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (YARN-75) RMContainer should handle a RELEASE
event while RUNNING
Posted by "Siddharth Seth (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/YARN-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siddharth Seth updated YARN-75:
-------------------------------
Attachment: YARN-75_2.txt
Uses the RELEASED state, and includes the unit test file which I missed adding last time.
> RMContainer should handle a RELEASE event while RUNNING
> -------------------------------------------------------
>
> Key: YARN-75
> URL: https://issues.apache.org/jira/browse/YARN-75
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.1.0-alpha
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Attachments: YARN-75_2.txt, YARN-75.txt
>
>
> An AppMaster can send a container release at any point. Currently this results in an exception, if this is done while the RM considers the container to be RUNNING.
> The event not being processed correctly also implies that these containers do not show up in the Completed Container List seen by the AM (AMRMProtocol). MR-3902 depends on this set being complete.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (YARN-75) RMContainer should handle a RELEASE
event while RUNNING
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/YARN-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450260#comment-13450260 ]
Hudson commented on YARN-75:
----------------------------
Integrated in Hadoop-Mapreduce-trunk-Commit #2724 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2724/])
YARN-75. Missing test. Ugh. (Revision 1381811)
Result = FAILURE
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1381811
Files :
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/TestRMContainerImpl.java
> RMContainer should handle a RELEASE event while RUNNING
> -------------------------------------------------------
>
> Key: YARN-75
> URL: https://issues.apache.org/jira/browse/YARN-75
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.1.0-alpha
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Fix For: 2.1.0-alpha
>
> Attachments: YARN-75_2.txt, YARN-75.txt
>
>
> An AppMaster can send a container release at any point. Currently this results in an exception, if this is done while the RM considers the container to be RUNNING.
> The event not being processed correctly also implies that these containers do not show up in the Completed Container List seen by the AM (AMRMProtocol). MR-3902 depends on this set being complete.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (YARN-75) RMContainer should handle a RELEASE
event while RUNNING
Posted by "Mayank Bansal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/YARN-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13446516#comment-13446516 ]
Mayank Bansal commented on YARN-75:
-----------------------------------
I think KILLED would be more appropriate then COMPLETED. COMPLETED would have been confusing in some cases.
Thanks,
Mayank
> RMContainer should handle a RELEASE event while RUNNING
> -------------------------------------------------------
>
> Key: YARN-75
> URL: https://issues.apache.org/jira/browse/YARN-75
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.1.0-alpha
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Attachments: YARN-75.txt
>
>
> An AppMaster can send a container release at any point. Currently this results in an exception, if this is done while the RM considers the container to be RUNNING.
> The event not being processed correctly also implies that these containers do not show up in the Completed Container List seen by the AM (AMRMProtocol). MR-3902 depends on this set being complete.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (YARN-75) RMContainer should handle a RELEASE
event while RUNNING
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/YARN-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450218#comment-13450218 ]
Hudson commented on YARN-75:
----------------------------
Integrated in Hadoop-Hdfs-trunk-Commit #2763 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2763/])
YARN-75. Missing test. Ugh. (Revision 1381811)
YARN-75. Added file missing from previous commit. Bad day with svn. (Revision 1381809)
YARN-75. Removing spurious file from the previous commit. (Revision 1381807)
YARN-75. Modified ResourceManager's RMContainer to handle a valid RELEASE event at RUNNING state. Contributed by Siddharth Seth. (Revision 1381806)
Result = SUCCESS
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1381811
Files :
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/TestRMContainerImpl.java
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1381809
Files :
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/TestRMContainerImpl.java
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1381807
Files :
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/TestRMContainerImpl.java.orig
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1381806
Files :
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/api/protocolrecords/AllocateRequest.java
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/RMContainerImpl.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/rmcontainer
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/TestRMContainerImpl.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/rmcontainer/TestRMContainerImpl.java.orig
> RMContainer should handle a RELEASE event while RUNNING
> -------------------------------------------------------
>
> Key: YARN-75
> URL: https://issues.apache.org/jira/browse/YARN-75
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.1.0-alpha
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Fix For: 2.1.0-alpha
>
> Attachments: YARN-75_2.txt, YARN-75.txt
>
>
> An AppMaster can send a container release at any point. Currently this results in an exception, if this is done while the RM considers the container to be RUNNING.
> The event not being processed correctly also implies that these containers do not show up in the Completed Container List seen by the AM (AMRMProtocol). MR-3902 depends on this set being complete.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (YARN-75) RMContainer should handle a RELEASE
event while RUNNING
Posted by "Robert Joseph Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/YARN-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Joseph Evans updated YARN-75:
------------------------------------
Fix Version/s: 0.23.4
I pulled this into branch-0.23
> RMContainer should handle a RELEASE event while RUNNING
> -------------------------------------------------------
>
> Key: YARN-75
> URL: https://issues.apache.org/jira/browse/YARN-75
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.0.0-alpha
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Fix For: 2.0.2-alpha, 0.23.4
>
> Attachments: YARN-75_2.txt, YARN-75.txt
>
>
> An AppMaster can send a container release at any point. Currently this results in an exception, if this is done while the RM considers the container to be RUNNING.
> The event not being processed correctly also implies that these containers do not show up in the Completed Container List seen by the AM (AMRMProtocol). MR-3902 depends on this set being complete.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (YARN-75) RMContainer should handle a RELEASE event
while RUNNING
Posted by "Arun C Murthy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/YARN-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arun C Murthy closed YARN-75.
-----------------------------
> RMContainer should handle a RELEASE event while RUNNING
> -------------------------------------------------------
>
> Key: YARN-75
> URL: https://issues.apache.org/jira/browse/YARN-75
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.0.0-alpha
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Fix For: 2.0.2-alpha, 0.23.4
>
> Attachments: YARN-75_2.txt, YARN-75.txt
>
>
> An AppMaster can send a container release at any point. Currently this results in an exception, if this is done while the RM considers the container to be RUNNING.
> The event not being processed correctly also implies that these containers do not show up in the Completed Container List seen by the AM (AMRMProtocol). MR-3902 depends on this set being complete.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (YARN-75) RMContainer should handle a RELEASE
event while RUNNING
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/YARN-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450234#comment-13450234 ]
Hudson commented on YARN-75:
----------------------------
Integrated in Hadoop-Mapreduce-trunk-Commit #2723 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2723/])
YARN-75. Added file missing from previous commit. Bad day with svn. (Revision 1381809)
YARN-75. Removing spurious file from the previous commit. (Revision 1381807)
YARN-75. Modified ResourceManager's RMContainer to handle a valid RELEASE event at RUNNING state. Contributed by Siddharth Seth. (Revision 1381806)
Result = FAILURE
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1381809
Files :
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/TestRMContainerImpl.java
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1381807
Files :
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/TestRMContainerImpl.java.orig
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1381806
Files :
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/api/protocolrecords/AllocateRequest.java
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/RMContainerImpl.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/rmcontainer
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/TestRMContainerImpl.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/rmcontainer/TestRMContainerImpl.java.orig
> RMContainer should handle a RELEASE event while RUNNING
> -------------------------------------------------------
>
> Key: YARN-75
> URL: https://issues.apache.org/jira/browse/YARN-75
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.1.0-alpha
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Fix For: 2.1.0-alpha
>
> Attachments: YARN-75_2.txt, YARN-75.txt
>
>
> An AppMaster can send a container release at any point. Currently this results in an exception, if this is done while the RM considers the container to be RUNNING.
> The event not being processed correctly also implies that these containers do not show up in the Completed Container List seen by the AM (AMRMProtocol). MR-3902 depends on this set being complete.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (YARN-75) RMContainer should handle a RELEASE
event while RUNNING
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/YARN-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450586#comment-13450586 ]
Hudson commented on YARN-75:
----------------------------
Integrated in Hadoop-Hdfs-trunk #1158 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1158/])
YARN-75. Missing test. Ugh. (Revision 1381811)
YARN-75. Added file missing from previous commit. Bad day with svn. (Revision 1381809)
YARN-75. Removing spurious file from the previous commit. (Revision 1381807)
YARN-75. Modified ResourceManager's RMContainer to handle a valid RELEASE event at RUNNING state. Contributed by Siddharth Seth. (Revision 1381806)
Result = FAILURE
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1381811
Files :
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/TestRMContainerImpl.java
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1381809
Files :
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/TestRMContainerImpl.java
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1381807
Files :
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/TestRMContainerImpl.java.orig
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1381806
Files :
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/api/protocolrecords/AllocateRequest.java
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/RMContainerImpl.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/rmcontainer
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/TestRMContainerImpl.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/rmcontainer/TestRMContainerImpl.java.orig
> RMContainer should handle a RELEASE event while RUNNING
> -------------------------------------------------------
>
> Key: YARN-75
> URL: https://issues.apache.org/jira/browse/YARN-75
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.1.0-alpha
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Fix For: 2.1.0-alpha
>
> Attachments: YARN-75_2.txt, YARN-75.txt
>
>
> An AppMaster can send a container release at any point. Currently this results in an exception, if this is done while the RM considers the container to be RUNNING.
> The event not being processed correctly also implies that these containers do not show up in the Completed Container List seen by the AM (AMRMProtocol). MR-3902 depends on this set being complete.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira