Judging from the epic description, this seems to target the oversubscription of reserved resources ?on the framework level.
However, my question was targeting the task level, where one task of a framework is requesting more RAM than it actually uses, and another tasks from the same framework can be started as revocable and use those slack resources. The latter is already possible with compressible resources such as CPU or bandwidth. I am now interested in non-compressible resources (i.e. memory). ________________________________ From: Guangya Liu <[email protected]> Sent: Monday, March 21, 2016 15:53 To: [email protected] Subject: Re: Current state of the oversubscription feature https://issues.apache.org/jira/browse/MESOS-4967 is planning to introduce "Oversubscription for reservation", can you please help check if this help? Thanks, Guangya On Mon, Mar 21, 2016 at 8:54 PM, Erb, Stephan <[email protected]<mailto:[email protected]>> wrote: Hi everyone, I am interested in the current state of the Mesos oversubscription feature [1]. In particular, I would like to know if anyone has taken a closer look at non-compressible resources such as memory. Anything I should be aware of? Thanks and Best Regards, Stephan [1] http://mesos.apache.org/documentation/latest/oversubscription/
