Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-2869

CapacityScheduler should trim sub queue names when parse configuration

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Reviewed

    Description

      Currently, capacity scheduler doesn't trim sub queue name when parsing queue names, for example, the configuration

      <configuration>
           <property>
               <name>...root.queues</name>
               <value> a, b  , c</value>
           </property>
      
           <property>
               <name>...root.b.capacity</name>
               <value>100</value>
           </property>
            
           .......
      </property>
      

      Will fail with error:

      java.lang.IllegalArgumentException: Illegal capacity of -1.0 for queue root. a 
      	at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacitySchedulerConfiguration.getCapacity(CapacitySchedulerConfiguration.java:332)
      	at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.getCapacityFromConf(LeafQueue.java:196)
              ....
      

      It will try to find a queues with name " a", " b ", and " c", which is apparently wrong, we should do trimming on these sub queue names.

      Attachments

        1. YARN-2869-3.patch
          7 kB
          Wangda Tan
        2. YARN-2869-2.patch
          7 kB
          Wangda Tan
        3. YARN-2869-1.patch
          5 kB
          Wangda Tan

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            leftnoteasy Wangda Tan Assign to me
            leftnoteasy Wangda Tan
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment