Re: Using mesos' cfs limits on a docker container?

Personally, I suggest to use the approach @Joseph and @Avinash mentioned. Because zhitao and my patches require Docker >= 1.7.0 . On Mon, Aug 15, 2016 at 1:27 AM, haosdent wrote: > Not sure if this related to https://issues.apache.org/ > jira/browse/MESOS-2154 > So far we

Re: Using mesos' cfs limits on a docker container?

Hi Mark, That would be awesome (user facing documentation forthe `UnifiedContainerizer`). We have bits and pieces of the unified containerizer (and what it actually is), but would be great to land a more comprehensive documentation into its motivation and usability. May be have a separate

Re: Using mesos' cfs limits on a docker container?

What was the problem and how did you overcome it? (i.e. This would be a sad resolution to this thread for someone faced with this same problem in the future.) On Sunday, August 14, 2016, Mark Hammons wrote: > I finally got this working after fiddling with it all

Re: Using mesos' cfs limits on a docker container?

In specific, I wanted the process control capabilities of a mesos framework with custom schedulers and executors, but wanted to run my tasks in a framework definable environment (like running my tasks on a copy of Ubuntu 14 with certain libs installed). Using mixed-mode containerization worked

Re: Using mesos' cfs limits on a docker container?

Not sure if this related to https://issues.apache.org/jira/browse/MESOS-2154 So far we have a quick workaround: specify the `cpu-period` and `cpu-quota` in the parameters field of `DockerInfo`. Then `Docker::run` would delegate this to the docker daemon. And recently zhitao and me work on the fix

Re: Using mesos' cfs limits on a docker container?

I finally got this working after fiddling with it all night. It works great so far! Mark Edgar Hammons II - Research Engineer at BioEmergences 0603695656 > On 14 Aug 2016, at 04:50, Joseph Wu wrote: > > If you're not against running Docker containers without the Docker

Re: Using mesos' cfs limits on a docker container?

Hi Mark, Good to hear you figured it out. Can you please post curl errors that you were observing and describe your image repository setup? I'd like to make sure that we have instructions on how to mitigate those. Artem. On Sunday, August 14, 2016, Mark Hammons

Re: Mesos loses track of Docker containers

Thank you, Sivaram. That would seem to be 2 "votes" for upgrading. -Paul > On Aug 13, 2016, at 11:47 PM, Sivaram Kannan wrote: > > > I don't remember the condition exactly, but I have faced similar issue in my > deployments and have been fixed when I moved to 0.26.0.

Re: resources in Mesos UI but none given to Spark

Problem solved-- I was incorrectly specifying the spark directory in the command-line argument. It wants the spark root directory, not the bin. I unpacked mine in /opt, so, the Right way: spark.mesos.executor.home=/opt/spark-2.0.0-bin-hadoop2.7/ Wrong way:

Re: Debugging Scheduler HTTP API Failures

HinZameer, when you send the SUBSCRIBE to Mesos, the response will contain a header 'Mesos-Stream-Id'. You have to send that header with every subsequent call you send to Mesos for that framework. -- Dario > On Aug 14, 2016, at 5:58 PM, Zameer Manji wrote: > > Hey, > >

Re: Debugging Scheduler HTTP API Failures

Oh, sorry, I didn't see you actually set the header (wall of text ;) ). That's an interesting issue, do you set the header case sensitive? I know headers shouldn't be case sensitive, but maybe there's a bug in the Mesos code. I have not seen this issue before. > On Aug 14, 2016, at 5:58 PM,

what's the difference between mesos and yarn?

Hi guys, What's the difference between yarn and mesos in practice? If using yarn, does container still needed? Thanks, Jared, (??) Software developer Interested in open source software, big data, Linux