[Meetup] Bangalore's first Mesos Meetup

Hi All, Happy to announce Bangalore's first Mesos Meetup at Huawei R campus. All are welcome. Please RSVP at the below link https://www.meetup.com/Bangalore-Mesos-cncf-User-Group/events/228745899/ Anyone wants to present or talk about Apache Mesos please let us know. Regards, Dhilip

Re: Initial Design Document Apache Mesos Federation (JIRA 3548)

Hi All, Sorry for the long gap. We had an interesting discussion last week at Mesosphere HQ again on this topic before the Mesos SF Meetup. The discussion revolved around several areas and suggestions on the proposed design. One of the main item that popped up was the approach through which we

1.0.1 release

Hi, As discussed on the 1.0 voting thread, we plan to cut a 1.0.1 as early as this week. So if you have anything that needs to absolutely go into the patch release, please work with your shepherd and get it landed on trunk and backported to the 1.0.x branch. Thanks,

Re: Enabling basic access authentication

We separated out the default authentication mode for read only (default: no authn) and read-write (default: authn) endpoints. Since the webui only depends on the read-only endpoints you need to explicitly enable authn for read-only endpoints if you need authn. See

Re: Enabling basic access authentication

It was working for me with mesos 1.0.0-rc2. Now that I made the switch to 1.0.0 the feature is missing for user/pass prompt at the WebUI. Was another flag added or was it decided that this feature wasn't necessary? On Tue, Jul 12, 2016 at 6:26 PM, Douglas Nelson wrote: >

Re: Attributes cause agent to fail

That showed me what wasn't working. If you start the mesos agent at all before setting attributes (or if you change attributes) you need to make sure it doesn't recover old live executors. The error: Failed to perform recovery: Incompatible agent info detected. The solution: Step 1: rm -f

Re: Running a mesos executor within a container....

I think you need du -sh /mnt/mesos/sandbox in the container because it is the mounted path of the sandbox in the docker container. On Mon, Aug 1, 2016 at 8:21 PM, Mark Hammons wrote: > I'll double check, but last time I du -sh the var folder in the container > it

Re: Log the print out instead of print screen

You could specific the `--log_dir` when you start mesos master and agents. For example, if you start master and agents with `--log_dir=/var/log/mesos`, all the logs would generate under `/var/log/mesos`. On Mon, Aug 1, 2016 at 7:47 PM, Bryan Fok wrote: > Hi > > How do

Re: never finish unresponsive tasks

Hi, it is impossible to allocate unlimited memory to tasks. Could your tasks always finish in a fixed memory resource range? If so, you could choose a max value of that range. On Mon, Aug 1, 2016 at 7:54 PM, Bryan Fok wrote: > Sometimes there are a few tasks (depend on

RE: Cadvisor and Mesos: cgroup monitoring

My bad. I forgot to restart the tasks. It works fine. Thanks again. De : haosdent [mailto:haosd...@gmail.com] Envoyé : lundi 1 août 2016 16:10 À : user Objet : Re: Cadvisor and Mesos: cgroup monitoring Hi, which mesos version you used? cgroups/devices is available since

Re: Cadvisor and Mesos: cgroup monitoring

Hi, which mesos version you used? cgroups/devices is available since 1.0.0 On Mon, Aug 1, 2016 at 8:10 PM, Aurélien DEHAY wrote: > Hi. > > > Adding cgroups/devices does not work, the /proc/x/task/x/cgroup does not > list the mesos cgroup under devices. > > > I will try

Re: Running a mesos executor within a container....

I'll double check, but last time I du -sh the var folder in the container it was too small to contain the binaries I downloaded. Mark Edgar Hammons II - Research Engineer at BioEmergences 0603695656 > On 01 Aug 2016, at 03:57, haosdent wrote: > > >First, the binaries I get

RE: Cadvisor and Mesos: cgroup monitoring

Hi. Adding cgroups/devices does not work, the /proc/x/task/x/cgroup does not list the mesos cgroup under devices. I will try snap with the plugin from Roger. Thanks. De : haosdent Envoyé : vendredi 29 juillet 2016 17:30:20 À : user

never finish unresponsive tasks

Sometimes there are a few tasks (depend on how many tasks have submitted) never complete, and no error return either. When I see this, I will increase the "mem" in the task.resources and it solve the problem. I dont think modify it every time when we encounter this problem is a good solution. Is

Log the print out instead of print screen

Hi How do I redirect the default print screen messages to log file (preferable to the log file create by loggin module)? I0801 10:53:40.08255139 group.cpp:427] Trying to create path '/mesos' in ZooKeeper I0801 10:53:40.08376830 detector.cpp:152] Detected a new leader: (id='9') I0801