hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ChenFolin (JIRA)" <j...@apache.org>
Subject [jira] [Created] (YARN-5188) FairScheduler performance bug
Date Wed, 01 Jun 2016 04:24:12 GMT
ChenFolin created YARN-5188:

             Summary: FairScheduler performance bug
                 Key: YARN-5188
                 URL: https://issues.apache.org/jira/browse/YARN-5188
             Project: Hadoop YARN
          Issue Type: Bug
          Components: fairscheduler
    Affects Versions: 2.5.0, 2.8.0
            Reporter: ChenFolin

 My Hadoop Cluster has recently encountered a performance problem. Details as Follows.
       The efficiency of assign container in the Resourcemanager may fall when the number
of running and pending application grows. And the fact is the cluster has too many PendingMB
or PengdingVcore , and the Cluster 
current utilization rate may below 20%.
       I checked the resourcemanager logs, I found that every assign container may cost 5
~ 10 ms, but just 0 ~ 1 ms at usual time.
       I use TestFairScheduler to reproduce the scene:
       Just one queue: root.defalut
     10240 apps.
       assign container avg time:  6753.9 us ( 6.7539 ms)  
     apps sort time (FSLeafQueue : Collections.sort(runnableApps, comparator); ): 4657.01
us ( 4.657 ms )
     compute LeafQueue Resource usage : 905.171 us ( 0.905171 ms )
     When just root.default, one assign container op contains : ( one apps sort op ) + 2 *
( compute leafqueue usage op )
       According to the above situation, I think the assign container op has a performance
problem  . 

This message was sent by Atlassian JIRA

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

View raw message