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

Move scheduler HTTP API parsing out of master process

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.5.0
    • Fix Version/s: None
    • Component/s: HTTP API, master
    • Labels:
      None

      Description

      Today all calls sent to Mesos via the v1 api are parsed in the master process, even though non of the information contained in that process is required for this. The master process is already doing the majority of the work and is the biggest bottleneck, so anything that can be done elsewhere would improve the situation. Parsing of the calls (and some validation) couldĀ be done in separate processes and in parallel for multiple frameworks, which should improve overall responsiveness and throughput of the master process.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              drexin Dario Rexin

              Dates

              • Created:
                Updated:

                Issue deployment