Hadoop Map/Reduce
  1. Hadoop Map/Reduce
  2. MAPREDUCE-2876

ContainerAllocationExpirer appears to use the incorrect configs

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 0.23.0
    • Fix Version/s: 0.23.0
    • Component/s: mrv2
    • Labels:
      None

      Description

      ContainerAllocationExpirer sets the expiration interval to be RMConfig.CONTAINER_LIVELINESS_MONITORING_INTERVAL but uses AMLIVELINESS_MONITORING_INTERVAL as the interval. This is very different from what AMLivelinessMonitor does.

      There should be two configs RMConfig.CONTAINER_LIVELINESS_MONITORING_INTERVAL for the monitoring interval and RMConfig.CONTAINER_EXPIRY_INTERVAL for the expiry.

        Issue Links

          Activity

          Hide
          Robert Joseph Evans added a comment -

          This issue should wait until MAPREDUCE-2864 is finished, because it will rename and move the configs that are going to be modified.

          Show
          Robert Joseph Evans added a comment - This issue should wait until MAPREDUCE-2864 is finished, because it will rename and move the configs that are going to be modified.
          Hide
          Mahadev konar added a comment -

          I think we might be using too many variables here. If you take a look at AbstractLivenessMonitor, you'll see that the monitor interval is derived from expiry interval which is probably what we should keep. We dont have to use different conf knobs for monitor interval and expiry interval.

          Show
          Mahadev konar added a comment - I think we might be using too many variables here. If you take a look at AbstractLivenessMonitor, you'll see that the monitor interval is derived from expiry interval which is probably what we should keep. We dont have to use different conf knobs for monitor interval and expiry interval.
          Hide
          Robert Joseph Evans added a comment -

          That is fine, and I am happy to change things however you want. But I don't see AbstractLivenessMonitor deriving one value from another. Currently on Trunk it has two methods.

            protected void setExpireInterval(int expireInterval) {
              this.expireInterval = expireInterval;
            }
          
            protected void setMonitorInterval(int monitorInterval) {
              this.monitorInterval = monitorInterval;
            }
          

          I don't see anywhere that they are derived from one another.

          AMLivelinessMonitor, ContainerAllocationExpirer, and NMLivelinessMonitor, all of them extend AbstractLivnessMonitor. AM liveness has two configs AM_EXPIRY_INTERVAL and AMLIVELINESS_MONITORING_INTERVAL. NM liveness does too NM_EXPIRY_INTERVAL and NMLIVELINESS_MONITORING_INTERVAL. But container has only one. CONTAINER_LIVELINESS_MONITORING_INTERVAL. Its value looks like a copy and paste error and has the same value as AMLIVELINESS_MONITORING_INTERVAL. It also uses AMLIVELINESS_MONITORING_INTERVAL as the expiry interval.

          If you want monitor interval derived from expiry that is fine. Should I set it to something like 0.5 * expiry? If so I will then rename this issue.

          Show
          Robert Joseph Evans added a comment - That is fine, and I am happy to change things however you want. But I don't see AbstractLivenessMonitor deriving one value from another. Currently on Trunk it has two methods. protected void setExpireInterval( int expireInterval) { this .expireInterval = expireInterval; } protected void setMonitorInterval( int monitorInterval) { this .monitorInterval = monitorInterval; } I don't see anywhere that they are derived from one another. AMLivelinessMonitor, ContainerAllocationExpirer, and NMLivelinessMonitor, all of them extend AbstractLivnessMonitor. AM liveness has two configs AM_EXPIRY_INTERVAL and AMLIVELINESS_MONITORING_INTERVAL. NM liveness does too NM_EXPIRY_INTERVAL and NMLIVELINESS_MONITORING_INTERVAL. But container has only one. CONTAINER_LIVELINESS_MONITORING_INTERVAL. Its value looks like a copy and paste error and has the same value as AMLIVELINESS_MONITORING_INTERVAL. It also uses AMLIVELINESS_MONITORING_INTERVAL as the expiry interval. If you want monitor interval derived from expiry that is fine. Should I set it to something like 0.5 * expiry? If so I will then rename this issue.
          Hide
          Mahadev konar added a comment -

          Sorry Bobby,
          I should have mentioned this. In the code:

          
            private int expireInterval = DEFAULT_EXPIRE;
            private int monitorInterval = expireInterval/3;
          

          It tries to do it in default values, unless set, maybe we should use 1/3rd to set monitor interval. Do you see any scenario where this wont work?

          Show
          Mahadev konar added a comment - Sorry Bobby, I should have mentioned this. In the code: private int expireInterval = DEFAULT_EXPIRE; private int monitorInterval = expireInterval/3; It tries to do it in default values, unless set, maybe we should use 1/3rd to set monitor interval. Do you see any scenario where this wont work?
          Hide
          Robert Joseph Evans added a comment -

          The issue is with granularity and how far off from the expire interval the expire will actually be. In the worst case something will expire just under 1 monitor interval after it should have. The only issue would be if someone really needed that expiry to be much closer to the actual expire interval then 1/3 of it. I don't really see that as much of an issue for anything we have right now.

          I would propose that we modify LivnessMonitor to store expiry in a priority queue instead of a map. Then it can sleep just the amount of time needed before the next one expires. It is fairly simple and I have done this type of thing in the past. Then there is very little error from the expire interval, and we don't have to worry about a monitor interval at all.

          Show
          Robert Joseph Evans added a comment - The issue is with granularity and how far off from the expire interval the expire will actually be. In the worst case something will expire just under 1 monitor interval after it should have. The only issue would be if someone really needed that expiry to be much closer to the actual expire interval then 1/3 of it. I don't really see that as much of an issue for anything we have right now. I would propose that we modify LivnessMonitor to store expiry in a priority queue instead of a map. Then it can sleep just the amount of time needed before the next one expires. It is fairly simple and I have done this type of thing in the past. Then there is very little error from the expire interval, and we don't have to worry about a monitor interval at all.
          Hide
          Mahadev konar added a comment -

          bobby,
          I think we can leave the setMonitor API. I was saying something along the lines of:

          When creating NMLivenessMonitor:

          
          monitor.setExpiry(x);
          monitor.setMonitorInternval(x/3);
          
          

          So in case someone wants to use Livenessmonitor with almost the same interval as expiry can use it that way. Seems reasonable?

          Show
          Mahadev konar added a comment - bobby, I think we can leave the setMonitor API. I was saying something along the lines of: When creating NMLivenessMonitor: monitor.setExpiry(x); monitor.setMonitorInternval(x/3); So in case someone wants to use Livenessmonitor with almost the same interval as expiry can use it that way. Seems reasonable?
          Hide
          Robert Joseph Evans added a comment -

          Sure.

          Show
          Robert Joseph Evans added a comment - Sure.
          Hide
          Sharad Agarwal added a comment -

          Sorry missed it earlier and saw it now.

          I would propose that we modify LivnessMonitor to store expiry in a priority queue instead of a map. Then it can sleep just the amount of time needed before the next one expires. It is fairly simple and I have done this type of thing in the past. Then there is very little error from the expire interval, and we don't have to worry about a monitor interval at all.

          priority queue - This was exactly the same thing I was thinking the first time when I wrote. The reason I chose Map is as follows - We receive pings from AM/NM/Tasks etc very frequently in the order of 1-3 seconds. The no of insertions in the priority queue would be huge. The cumulative cost of multiple insertions in priority queue would be more than iterating over the whole list every few seconds. make sense ?

          Show
          Sharad Agarwal added a comment - Sorry missed it earlier and saw it now. I would propose that we modify LivnessMonitor to store expiry in a priority queue instead of a map. Then it can sleep just the amount of time needed before the next one expires. It is fairly simple and I have done this type of thing in the past. Then there is very little error from the expire interval, and we don't have to worry about a monitor interval at all. priority queue - This was exactly the same thing I was thinking the first time when I wrote. The reason I chose Map is as follows - We receive pings from AM/NM/Tasks etc very frequently in the order of 1-3 seconds. The no of insertions in the priority queue would be huge. The cumulative cost of multiple insertions in priority queue would be more than iterating over the whole list every few seconds. make sense ?
          Hide
          Robert Joseph Evans added a comment -

          I am fine with the polling like I said before. The question I was trying to answer was what is the ramifications of not having a polling interval, but just having an expiry interval, and setting the polling interval off of the expiry interval. It means the real expiry interval is any time between expiryInterval and expiryInterval + pollingInterval. If that is never a problem then polling is fine.

          I can see your reasoning behind the change. When there are N objects being tracked then polling would be

           O((pollingFrequency * N) + (modificationFrequency * N))
          

          But Priority Queue would be

          O(modificationFrequency * N * log(N) + expiryFrequency)
          

          So if the modificationFrequency is very large then polling definitely wins in complexity, but I am curious did you run any benchmarks to see what kind of an extra load would be placed on the system with a priority queue (Just curious what it might be)?

          Show
          Robert Joseph Evans added a comment - I am fine with the polling like I said before. The question I was trying to answer was what is the ramifications of not having a polling interval, but just having an expiry interval, and setting the polling interval off of the expiry interval. It means the real expiry interval is any time between expiryInterval and expiryInterval + pollingInterval. If that is never a problem then polling is fine. I can see your reasoning behind the change. When there are N objects being tracked then polling would be O((pollingFrequency * N) + (modificationFrequency * N)) But Priority Queue would be O(modificationFrequency * N * log(N) + expiryFrequency) So if the modificationFrequency is very large then polling definitely wins in complexity, but I am curious did you run any benchmarks to see what kind of an extra load would be placed on the system with a priority queue (Just curious what it might be)?
          Hide
          Sharad Agarwal added a comment -

          @Robert As you have mentioned, the modificationFrequency and N is quite high in most of our usecases. So based on computational complexities and also the code complexity, went for the simple polling model.

          Show
          Sharad Agarwal added a comment - @Robert As you have mentioned, the modificationFrequency and N is quite high in most of our usecases. So based on computational complexities and also the code complexity, went for the simple polling model.
          Hide
          Anupam Seth added a comment -

          Kindly review patch.

          Show
          Anupam Seth added a comment - Kindly review patch.
          Hide
          Robert Joseph Evans added a comment -

          Putting into patch available to kick Jenkins to get the test results. The patch mostly looks good. Are there any tests for AbstractLivenessMonitor? If not could you add in a simple one.

          Show
          Robert Joseph Evans added a comment - Putting into patch available to kick Jenkins to get the test results. The patch mostly looks good. Are there any tests for AbstractLivenessMonitor? If not could you add in a simple one.
          Hide
          Hadoop QA added a comment -

          -1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12498198/MAPREDUCE-2876-branch-0_23.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 javadoc. The javadoc tool did not generate any warning messages.

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

          +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 .

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

          Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/969//testReport/
          Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/969//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/12498198/MAPREDUCE-2876-branch-0_23.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 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +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 . +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/969//testReport/ Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/969//console This message is automatically generated.
          Hide
          Anupam Seth added a comment -

          There is a test TestNmLivelinessMonitor that seems to do a fairly thorough job of testing expiry. NMLivenessMonitor is a subclass from AbstractLivenessMonitor and AMLivenessMonitor and ContainerAllocatorExpirer do almost the same thing. Please let me know if you would like me to add tests for AMLivenessMonitor and ContainerAllocatorExpirer or enhance coverage of this existing test in some way.

          Show
          Anupam Seth added a comment - There is a test TestNmLivelinessMonitor that seems to do a fairly thorough job of testing expiry. NMLivenessMonitor is a subclass from AbstractLivenessMonitor and AMLivenessMonitor and ContainerAllocatorExpirer do almost the same thing. Please let me know if you would like me to add tests for AMLivenessMonitor and ContainerAllocatorExpirer or enhance coverage of this existing test in some way.
          Hide
          Robert Joseph Evans added a comment -

          All I really care about is a unit test to verify that the change is working correctly. If TestNmLivelenessMonitor covers it then that is OK by me.

          Show
          Robert Joseph Evans added a comment - All I really care about is a unit test to verify that the change is working correctly. If TestNmLivelenessMonitor covers it then that is OK by me.
          Hide
          Robert Joseph Evans added a comment -

          Thanks for the explanation +1 for the patch.

          Show
          Robert Joseph Evans added a comment - Thanks for the explanation +1 for the patch.
          Hide
          Mahadev konar added a comment -

          thanks anupam and bobby,
          Ill go ahead and commit this.

          Show
          Mahadev konar added a comment - thanks anupam and bobby, Ill go ahead and commit this.
          Hide
          Mahadev konar added a comment -

          sorry just noticed,

          I think we should leave the api still there:

          -  protected void setMonitorInterval(int monitorInterval) {
          -    this.monitorInterval = monitorInterval;
          -  }
          -
          

          Someone might want to use it with a different monitor interval, other than default (expiry/3).

          Show
          Mahadev konar added a comment - sorry just noticed, I think we should leave the api still there: - protected void setMonitorInterval( int monitorInterval) { - this .monitorInterval = monitorInterval; - } - Someone might want to use it with a different monitor interval, other than default (expiry/3).
          Hide
          Arun C Murthy added a comment -

          Cancelling patch while Mahadev's comments are addressed.

          Show
          Arun C Murthy added a comment - Cancelling patch while Mahadev's comments are addressed.
          Hide
          Anupam Seth added a comment -

          Thanks Mahadev!

          I removed also

          this.monitorInterval = expireIntervel/3;
          

          from

          AbstractLivelinessMonitor#setExpireInterval

          and moved it out to the subclasses to avoid the undesirable effect of silently setting a config param that they might have set apriori in the subclass by doing something like

          ...
          setMonitorInterval(expireIntvl/5);
          setExpireInterval(expireIntvl);
          ...
          
          Show
          Anupam Seth added a comment - Thanks Mahadev! I removed also this .monitorInterval = expireIntervel/3; from AbstractLivelinessMonitor#setExpireInterval and moved it out to the subclasses to avoid the undesirable effect of silently setting a config param that they might have set apriori in the subclass by doing something like ... setMonitorInterval(expireIntvl/5); setExpireInterval(expireIntvl); ...
          Hide
          Mahadev konar added a comment -

          +1 looks good to me. Will wait for hudson before checkin it in.

          Show
          Mahadev konar added a comment - +1 looks good to me. Will wait for hudson before checkin it in.
          Hide
          Hadoop QA added a comment -

          -1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12498251/MAPREDUCE-2876-branch-0_23.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 javadoc. The javadoc tool did not generate any warning messages.

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

          +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 .

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

          Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/972//testReport/
          Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/972//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/12498251/MAPREDUCE-2876-branch-0_23.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 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +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 . +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/972//testReport/ Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/972//console This message is automatically generated.
          Hide
          Arun C Murthy added a comment -

          I just committed this. Thanks Anupam!

          Show
          Arun C Murthy added a comment - I just committed this. Thanks Anupam!
          Hide
          Hudson added a comment -

          Integrated in Hadoop-Hdfs-trunk-Commit #1126 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/1126/)
          MAPREDUCE-2876. Use a different config for ContainerAllocationExpirer. Contributed by Anupam Seth.

          acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1180767
          Files :

          • /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
          • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java
          • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/NMLivelinessMonitor.java
          • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmapp/attempt/AMLivelinessMonitor.java
          • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/ContainerAllocationExpirer.java
          Show
          Hudson added a comment - Integrated in Hadoop-Hdfs-trunk-Commit #1126 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/1126/ ) MAPREDUCE-2876 . Use a different config for ContainerAllocationExpirer. Contributed by Anupam Seth. acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1180767 Files : /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/NMLivelinessMonitor.java /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmapp/attempt/AMLivelinessMonitor.java /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/ContainerAllocationExpirer.java
          Hide
          Hudson added a comment -

          Integrated in Hadoop-Common-trunk-Commit #1048 (See https://builds.apache.org/job/Hadoop-Common-trunk-Commit/1048/)
          MAPREDUCE-2876. Use a different config for ContainerAllocationExpirer. Contributed by Anupam Seth.

          acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1180767
          Files :

          • /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
          • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java
          • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/NMLivelinessMonitor.java
          • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmapp/attempt/AMLivelinessMonitor.java
          • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/ContainerAllocationExpirer.java
          Show
          Hudson added a comment - Integrated in Hadoop-Common-trunk-Commit #1048 (See https://builds.apache.org/job/Hadoop-Common-trunk-Commit/1048/ ) MAPREDUCE-2876 . Use a different config for ContainerAllocationExpirer. Contributed by Anupam Seth. acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1180767 Files : /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/NMLivelinessMonitor.java /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmapp/attempt/AMLivelinessMonitor.java /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/ContainerAllocationExpirer.java
          Hide
          Hudson added a comment -

          Integrated in Hadoop-Mapreduce-trunk-Commit #1068 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/1068/)
          MAPREDUCE-2876. Use a different config for ContainerAllocationExpirer. Contributed by Anupam Seth.

          acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1180767
          Files :

          • /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
          • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java
          • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/NMLivelinessMonitor.java
          • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmapp/attempt/AMLivelinessMonitor.java
          • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/ContainerAllocationExpirer.java
          Show
          Hudson added a comment - Integrated in Hadoop-Mapreduce-trunk-Commit #1068 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/1068/ ) MAPREDUCE-2876 . Use a different config for ContainerAllocationExpirer. Contributed by Anupam Seth. acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1180767 Files : /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/NMLivelinessMonitor.java /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmapp/attempt/AMLivelinessMonitor.java /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/ContainerAllocationExpirer.java
          Hide
          Hudson added a comment -

          Integrated in Hadoop-Hdfs-trunk #826 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk/826/)
          MAPREDUCE-2876. Use a different config for ContainerAllocationExpirer. Contributed by Anupam Seth.

          acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1180767
          Files :

          • /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
          • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java
          • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/NMLivelinessMonitor.java
          • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmapp/attempt/AMLivelinessMonitor.java
          • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/ContainerAllocationExpirer.java
          Show
          Hudson added a comment - Integrated in Hadoop-Hdfs-trunk #826 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk/826/ ) MAPREDUCE-2876 . Use a different config for ContainerAllocationExpirer. Contributed by Anupam Seth. acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1180767 Files : /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/NMLivelinessMonitor.java /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmapp/attempt/AMLivelinessMonitor.java /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/ContainerAllocationExpirer.java
          Hide
          Hudson added a comment -

          Integrated in Hadoop-Hdfs-0.23-Build #35 (See https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/35/)
          Merge -c 1180767 from trunk to branch-0.23 to fix MAPREDUCE-2876.

          acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1180768
          Files :

          • /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
          • /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java
          • /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/NMLivelinessMonitor.java
          • /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmapp/attempt/AMLivelinessMonitor.java
          • /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/ContainerAllocationExpirer.java
          Show
          Hudson added a comment - Integrated in Hadoop-Hdfs-0.23-Build #35 (See https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/35/ ) Merge -c 1180767 from trunk to branch-0.23 to fix MAPREDUCE-2876 . acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1180768 Files : /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/NMLivelinessMonitor.java /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmapp/attempt/AMLivelinessMonitor.java /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/ContainerAllocationExpirer.java
          Hide
          Hudson added a comment -

          Integrated in Hadoop-Mapreduce-0.23-Build #42 (See https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Build/42/)
          Merge -c 1180767 from trunk to branch-0.23 to fix MAPREDUCE-2876.

          acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1180768
          Files :

          • /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
          • /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java
          • /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/NMLivelinessMonitor.java
          • /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmapp/attempt/AMLivelinessMonitor.java
          • /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/ContainerAllocationExpirer.java
          Show
          Hudson added a comment - Integrated in Hadoop-Mapreduce-0.23-Build #42 (See https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Build/42/ ) Merge -c 1180767 from trunk to branch-0.23 to fix MAPREDUCE-2876 . acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1180768 Files : /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/NMLivelinessMonitor.java /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmapp/attempt/AMLivelinessMonitor.java /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/ContainerAllocationExpirer.java
          Hide
          Hudson added a comment -

          Integrated in Hadoop-Mapreduce-trunk #856 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/856/)
          MAPREDUCE-2876. Use a different config for ContainerAllocationExpirer. Contributed by Anupam Seth.

          acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1180767
          Files :

          • /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
          • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java
          • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/NMLivelinessMonitor.java
          • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmapp/attempt/AMLivelinessMonitor.java
          • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/ContainerAllocationExpirer.java
          Show
          Hudson added a comment - Integrated in Hadoop-Mapreduce-trunk #856 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/856/ ) MAPREDUCE-2876 . Use a different config for ContainerAllocationExpirer. Contributed by Anupam Seth. acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1180767 Files : /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/NMLivelinessMonitor.java /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmapp/attempt/AMLivelinessMonitor.java /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/ContainerAllocationExpirer.java
          Hide
          Anupam Seth added a comment -

          Thanks Bobby, Mahadev and Arun!

          Show
          Anupam Seth added a comment - Thanks Bobby, Mahadev and Arun!

            People

            • Assignee:
              Anupam Seth
              Reporter:
              Robert Joseph Evans
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development