How to manage maintenance windows?

Hi, Mesos provides nice support for maintenance managing since some versions. Thank you. The API provides all the required functionality but I couldn't found a tool for operators to manage maintenance windows. How do you manage/plan such windows? Did you integrate the API in your existing

Re: mess spark cluster mode error

Seems the classpath incorrect. Do you try package all dependencies into a assembly jar which contains "org.apache.spark.launcher.Main"? On Mon, Mar 14, 2016 at 9:56 PM, sjk wrote: > hi,all, when i run task on mesos, task error below. for help, thanks a > lot. > > >

Re: mess spark cluster mode error

I believe you are missing either —spark.executor.uri pointing to spark tar.gz or —spark.mesos.executor.home http://spark.apache.org/docs/latest/running-on-mesos.html#configuration Kind regards,
 Radek Gruchalski 
ra...@gruchalski.com (mailto:ra...@gruchalski.com)


Re: How to manage maintenance windows?

Managing maintenance is currently up to the operator (you, presumably). If you have something to contribute (code, docs, or examples), that would be greatly appreciated :) We haven't prioritized other integration (like the CLI or web UI) since maintenance primitives themselves need to be

RE: [VOTE] Release Apache Mesos 0.28.0 (rc2)

+1 (non-binding) Ran `sudo make check` on Centos 7. All tests passed. Also ran some runtime tests with unified containerizer launching docker images and regular mesos tasks, as well as some tasks using the docker containerizer. All working as expected Cheers, -Dan -Original Message-

Re: [VOTE] Release Apache Mesos 0.28.0 (rc2)

When running `sudo make check` on debian 8, I saw the following unaccounted test failure: [ FAILED ] ProvisionerDockerRegistryPullerTest.ROOT_INTERNET_CURL_ShellCommand (1129 ms) It seems to related to an error message with `Failed to change user to 'root': Failed to getgid: unknown user` I've

HTTP API

Hi all, since the introduction of the HTTP API in 0.24 around 7.5 months have passed. What are the plans to make this API stable? There are already features (inverse offers) that are exclusively available through this API, so it would be great to have a timeline, as I think for most people

Re: [VOTE] Release Apache Mesos 0.25.1 (rc2)

On Sun, Mar 13, 2016 at 3:46 PM, Michael Park wrote: > Hi Evan, > > If we wanted to backport those patches as well, we should cut a 0.25.2. > I would first like to understand what kind of issues you're running into. > Do you mind elaborating a little? > For MESOS-3738, we ran

running mesos slave in a docker container

Since mesosphere distributes images of mesos software in a container ( https://hub.docker.com/r/mesosphere/mesos-slave/), I decided to try this option. After trying this with various settings I settled on a configuration that basically works. But I do see one problem and this is what this message

Re: [VOTE] Release Apache Mesos 0.28.0 (rc2)

Maybe fill a ticket in https://issues.apache.org/jira/browse/MESOS would be more convenience for further discussion. By the way, could "OsTest.User" pass in your machine? It also call "os::getgid" during test. On Tue, Mar 15, 2016 at 6:57 AM, Zhitao Li wrote: > When

RE: running mesos slave in a docker container

One way to avoid map library dependencies of docker between host and docker containers is to install binaries of docker into the docker container: https://docs.docker.com/engine/installation/binaries/ and then map /var/run/docker.sock between host and docker containers. In this way, library

Re: running mesos slave in a docker container

Sure, but my point what - why would mesosphere not put docker binary in the official docker image? Maintaining my own docker image of anything is the last instrument I use. That's what "official" images are for after all. On Mon, Mar 14, 2016 at 8:30 PM, Yong Tang

mess spark cluster mode error

hi,all, when i run task on mesos, task error below. for help, thanks a lot. cluster mode, command: $SPARK_HOME/spark-submit --class com.xxx.ETL --master mesos://192.168.191.116:7077 --deploy-mode cluster --supervise --driver-memory 2G --executor-memory 10G — total-executor-cores 4

RE: Mesos 0.27 and docker

The args did the trick { … "args": [ "--application=Test", "--instance=Test" ] … } Regards Walter From: Tim Chen [mailto:t...@mesosphere.io] Sent: 11 March 2016 18:41 To: user@mesos.apache.org Subject: Re: Mesos 0.27 and docker Hi Walter, The parameters field in the

Re: running mesos slave in a docker container

Enumerating each and every lib path and dealing with potential conflicts between host and docker libc, etc - I didn't want to deal with this option, it's quite bad imho. On Mon, Mar 14, 2016 at 6:42 PM, haosdent wrote: > >2. --volumes-from > So far DockerContainerizer in

Re: running mesos slave in a docker container

>2. --volumes-from So far DockerContainerizer in Mesos don't support this option. >1. What is the best method to point mesos-slave running in a container to a working Usually I mount docker binary to container from host. ``` docker run --privileged -d \ --name=mesos-slave \ --net=host \ -p

Re: [VOTE] Release Apache Mesos 0.28.0 (rc2)

Filed https://issues.apache.org/jira/browse/MESOS-4946 to track. All "OsTest" passes under root on my machine. On Mon, Mar 14, 2016 at 6:30 PM, haosdent wrote: > Maybe fill a ticket in https://issues.apache.org/jira/browse/MESOS would > be more convenience for further