hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7636) Re-reservation count may overflow when cluster resource exhausted for a long time
Date Fri, 16 Mar 2018 11:36:00 GMT

    [ https://issues.apache.org/jira/browse/YARN-7636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16401777#comment-16401777
] 

Hudson commented on YARN-7636:
------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13848 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/13848/])
YARN-7636. Re-reservation count may overflow when cluster resource (wwei: rev 154cfb2b620002a7d3b7fdbf8b68236c432771e1)
* (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/SchedulerApplicationAttempt.java


> Re-reservation count may overflow when cluster resource exhausted for a long time 
> ----------------------------------------------------------------------------------
>
>                 Key: YARN-7636
>                 URL: https://issues.apache.org/jira/browse/YARN-7636
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacityscheduler
>    Affects Versions: 3.1.0, 2.9.1
>            Reporter: Tao Yang
>            Assignee: Tao Yang
>            Priority: Major
>             Fix For: 3.1.0, 2.9.1, 3.0.2, 3.2.0
>
>         Attachments: YARN-7636.001.patch, YARN-7636.002.patch, YARN-7636.003.patch
>
>
> This happens on our production cluster twice, when a request cannot be satisfied for
a long time, it continually triggers the re-reservation and eventually caused the overflow.
This will crash the scheduler.
> Exception stack:
> {noformat}
> java.lang.IllegalArgumentException: Overflow adding 1 occurrences to a count of 2147483647
>         at com.google.common.collect.ConcurrentHashMultiset.add(ConcurrentHashMultiset.java:246)
>         at com.google.common.collect.AbstractMultiset.add(AbstractMultiset.java:80)
>         at com.google.common.collect.ConcurrentHashMultiset.add(ConcurrentHashMultiset.java:51)
>         at org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerApplicationAttempt.addReReservation(SchedulerApplicationAttempt.java:406)
>         at org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerApplicationAttempt.reserve(SchedulerApplicationAttempt.java:555)
>         at org.apache.hadoop.yarn.server.resourcemanager.scheduler.common.fica.FiCaSchedulerApp.reserve(FiCaSchedulerApp.java:1076)
>         at org.apache.hadoop.yarn.server.resourcemanager.scheduler.common.fica.FiCaSchedulerApp.apply(FiCaSchedulerApp.java:795)
>         at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.tryCommit(CapacityScheduler.java:2770)
>         at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler$ResourceCommitterService.run(CapacityScheduler.java:546)
> {noformat}
> Refer to handling of SchedulerApplicationAttempt#addSchedulingOpportunity, we can ignore
this exception to avoid this problem.
> This problem may happens in SchedulerApplicationAttempt#addMissedNonPartitionedRequestSchedulingOpportunity,
fix it in the same way.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message