Re: [Design Doc] Improve Storage Support in Mesos using Resources Provider

Mesos at one point had a serious constraint that did not include network utilization as an ask. That proved to be a major issue in utilizing the frames (physical machines) effectively. If this has been resolved, I appologize for missing this amazingly important fix. Otherwise tweaking disk when

Re: Detect when mesos agent needs work directory cleanup

I would recommend avoiding a manual clean up of the work directory, since it's not guaranteed that this approach will remain correct as things evolve. To have the agent perform the cleanup using its own logic, you can run: mesos-agent --recover=cleanup --work_dir= --master= Also, there is

Re: [Design Doc] Improve Storage Support in Mesos using Resources Provider

Yes, the idea is to make this general in the future. In fact, the whole resource provider design keeps that in mind. We could add a general "CONVERT" operation in the future with a free formed key value pairs (as well as the source resources) as the parameters. And it's up to the corresponding

Re: Detect when mesos agent needs work directory cleanup

Thank you. I will do that then. Mike On Wed, Mar 22, 2017 at 6:57 PM, Tomek Janiszewski wrote: > 1. Cleanup in required when agent configuration is not compatible with > previous version. This mean task runtime change. This occurs when: > resources, isolators, attributes or

Re: [Design Doc] Improve Storage Support in Mesos using Resources Provider

Is the intent to make this generic beyond disks? I can see the concepts apply beyond volumes, and blocks. Perhaps a generic Create{generation} -- where larger generation numbers descend from smaller ones? I can also see this valuable in networking. My use case is ENIs in AWS. I would like to have