Uploaded image for project: 'Tajo'
  1. Tajo
  2. TAJO-1397

Resource allocation should be fine grained.

    Details

      Description

      See the comment:

      https://issues.apache.org/jira/browse/TAJO-540?focusedCommentId=14359478&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14359478

      From the discussion in TAJO-540

      In general, query (or job) scheduler aims at the maximum resource utilization. For multi-tenancy, we also need to consider the fairness for multiple users (or queries). BTW, the maximum resource utilization and fairness are usually conflict to each other in many cases. To mitigate this problem, many scheduler seems to use preemption approach.

      In this point, our resource and scheduler system has the following problems:

      • A query exclusively uses allocated resources at the first time until the query is completed or failed.
      • There is no mechanism to deallocate resources during query processing.
      • Preempt is also not allowed.

      To achieve the multi tenancy, we should change our resource circulation. Especially, resource allocation must be fine grained instead of per query.
      So, I'll create a jira issue to change the resource circulation. We have to do this issue firstly in my opinion. If we achieve this, implementing multi-tenant scheduler would be much easier than now. It would be a good starting point of this issue.

        Attachments

        1. old_resource_circuit.png
          226 kB
          Hyunsik Choi
        2. resource_circuit.png
          228 kB
          Hyunsik Choi
        3. ResoruceSequence.jpg
          37 kB
          Jinho Kim
        4. TAJO-1397.patch
          683 kB
          Jinho Kim
        5. TAJO-1397_2.patch
          758 kB
          Jinho Kim
        6. TAJO-1397_3.patch
          818 kB
          Jinho Kim
        7. TAJO-1397_4.patch
          818 kB
          Jinho Kim

          Issue Links

            Activity

              People

              • Assignee:
                jhkim Jinho Kim
                Reporter:
                hyunsik Hyunsik Choi
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: