[ 
https://issues.apache.org/jira/browse/MESOS-9497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17017367#comment-17017367
 ] 

Benjamin Mahler commented on MESOS-9497:
----------------------------------------

{noformat}
commit fae9ed4626e8073ff5f17f3d87448053252e2046
Author: Benjamin Mahler <bmah...@apache.org>
Date:   Mon Jan 6 12:56:19 2020 -0500

    Updated all GET_* v1 master calls to be served in parallel.

    Using the same approach taken for the v0 read-only endpoints,
    this enables parallel reads for the GET_* v1 master calls.

    Review: https://reviews.apache.org/r/71978
{noformat}

> Parallel reads for master v1 state calls
> ----------------------------------------
>
>                 Key: MESOS-9497
>                 URL: https://issues.apache.org/jira/browse/MESOS-9497
>             Project: Mesos
>          Issue Type: Improvement
>          Components: HTTP API, master
>            Reporter: Greg Mann
>            Assignee: Benjamin Mahler
>            Priority: Major
>              Labels: mesosphere, performance
>
> Similar to MESOS-9158 - we should make the operator API calls which serve 
> master state perform computation of multiple such responses in parallel to 
> reduce the performance impact on the master actor.
> Note that this includes the initial expensive SUBSCRIBE payload for the event 
> streaming API, which is less straightforward to incorporate into the parallel 
> serving logic since it performs writes (to track the subscriber) and produces 
> an infinite response, unlike the other state related calls.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to