Uploaded image for project: 'Mesos'
  1. Mesos
  2. MESOS-3341

Introduce Resource Resolution

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • None
    • None
    • None
    • None

    Description

      After MESOS-1807, Mesos containers require >= 0.01 CPU resources and >= 32MB Memory resources. In order to simplify accounting, Mesos should introduce resource resolution.

      For example, it is possible to launch a task with 1.0000000000001 CPU (as it exceeds the minimum number of CPUs and is therefore considered valid). The fractional component of this task does not benefit the running process, and can introduce floating point errors when Mesos is accounting its offers (which we have already seen happening in MESOS-1867 and MESOS-2635). A solution to this could be disallowing tasks with finer granularity than the required resolution.

      Attachments

        Issue Links

          is related to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. MESOS-3997 Switch to fixed-point for resources

          • Major - Major loss of function.
          • Accepted
          is superceded by

          Improvement - An improvement or enhancement to an existing feature or task. MESOS-4687 Implement reliable floating point for scalar resources

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              Unassigned Unassigned
              jessicalhartog Jessica Hartog
              Timothy Chen Timothy Chen
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: