mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mpereira <>
Subject [GitHub] mesos pull request #247: Fixed reference to Mesos paper in the documentation...
Date Sun, 05 Nov 2017 12:56:18 GMT
Github user mpereira commented on a diff in the pull request:
    --- Diff: docs/ ---
    @@ -34,4 +34,4 @@ In addition, this resource offer process repeats when tasks finish and
new resou
     While the thin interface provided by Mesos allows it to scale and allows the frameworks
to evolve independently, one question remains: how can the constraints of a framework be satisfied
without Mesos knowing about these constraints? For example, how can a framework achieve data
locality without Mesos knowing which nodes store the data required by the framework? Mesos
answers these questions by simply giving frameworks the ability to **reject** offers. A framework
will reject the offers that do not satisfy its constraints and accept the ones that do.  In
particular, we have found that a simple policy called delay scheduling, in which frameworks
wait for a limited time to acquire nodes storing the input data, yields nearly optimal data
    -You can also read much more about the Mesos architecture in this [technical paper](
    +You can also read much more about the Mesos architecture in this [technical paper](
    --- End diff --
    I [amended my commit](
to use the URL you suggested.
    Do you think it's still worth pinging someone about maybe fixing the broken URL [referenced
by external websites](


View raw message