mesos-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kota UENISHI <>
Subject Re: Fetcher cache: caching even more while an executor is alive
Date Tue, 05 Jul 2016 10:23:34 GMT
Thanks, it looks promising to me - I was aware of persistent volumes
because I thought the use case was different, like for databases. I'll
try it on.

As the document says

> persistent volumes are associated with roles,

this makes failure handling a little bit difficult - As my framework
is not handling failure well enough, those volume IDs must be
remembered during framework restart or failover, or must get recovered
after.  Restarted framework must reuse or collect already reserved
volumes or those volumes just gets leaking.


On Tue, Jul 5, 2016 at 6:03 PM, Aaron Carey <> wrote:
> As you're writing the framework, have you looked at reserving persistent volumes? I think
it might help in your use case:
> Aaron
> --
> Aaron Carey
> Production Engineer - Cloud Pipeline
> Industrial Light & Magic
> London
> 020 3751 9150
> ________________________________________
> From: 上西康太 []
> Sent: 05 July 2016 08:24
> To:
> Subject: Fetcher cache: caching even more while an executor is alive
> Hi,
> I'm developing my own framework - that distributes >100 independent
> tasks across the cluster and just run them arbitrarily. My problem is,
> each task execution environment is a bit large tarball (2~6GB, mostly
> application jar files) and task itself finishes within 1~200 seconds,
> while tarball extraction takes like tens of seconds every time.
> Extracting the same tarball again and again in all tasks is a wasteful
> overhead that cannot be ignored.
> Fetcher cache is great, but in my case, fetcher cache isn't even
> enough and I want to preserve all files extracted from the tarball
> while my executor is alive. If Mesos could cache all files extracted
> from the tarball by omitting not only download but extraction, I could
> save more time.
> In "Fetcher Cache Internals" [1] or in "Fetcher Cache" [2] section in
> the official document, such issues or future work is not mentioned -
> how do you solve this kind of extraction overhead problem, when you
> have rather large resource ?
> An option would be setting up an internal docker registry and let
> slaves cache the docker image that includes our jar files and save
> tarball extraction. But, I want to prevent our system from additional
> moving parts as much as I can.
> Another option might be let fetcher fetch all jar files independently
> in slaves, but I think it feasible, but I don't think it manageable in
> production in an easy way.
> PS Mesos is great; it is helping us a lot - I want to appreciate all
> the efforts by the community. Thank you so much!
> [1]
> [2]

View raw message