Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-17010

Add queue capacity weights support in FairCallQueue

    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 3.4.0
    • ipc
    • None
    • Reviewed
    • Hide
      When FairCallQueue is enabled, user can specify capacity allocation among all sub-queues via configuration “ipc.<port>.callqueue.capacity.weights”. The value of this config is a comma-separated list of positive integers, each of which specifies the weight associated with the sub-queue at that index. This list length should be IPC scheduler priority levels, defined by "scheduler.priority.levels".

      By default, each sub-queue is associated with weight 1, i.e., all sub-queues are allocated with the same capacity.
      Show
      When FairCallQueue is enabled, user can specify capacity allocation among all sub-queues via configuration “ipc.<port>.callqueue.capacity.weights”. The value of this config is a comma-separated list of positive integers, each of which specifies the weight associated with the sub-queue at that index. This list length should be IPC scheduler priority levels, defined by "scheduler.priority.levels". By default, each sub-queue is associated with weight 1, i.e., all sub-queues are allocated with the same capacity.

    Description

      Right now in FairCallQueue all subqueues share the same capacity by evenly distributing total capacity. This requested feature is to make subqueues able to have different queue capacity where more important queues can have more capacity, thus less queue overflow and client backoffs.

      Attachments

        1. HADOOP-17010.001.patch
          10 kB
          Fengnan Li
        2. HADOOP-17010.002.patch
          10 kB
          Fengnan Li

        Issue Links

          Activity

            People

              fengnanli Fengnan Li
              fengnanli Fengnan Li
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: