Re: 1.0.2 release

Release dashboard: https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12329719 I'm waiting for 2 issues to be resolved. Once that's done, I'll start prepping the release. On Wed, Oct 5, 2016 at 4:11 PM, Vinod Kone wrote: > Hi, > > As the Release Manager for

1.0.2 release

Hi, As the Release Manager for 1.0, I'm responsible for all subsequent patch releases. I'm planning to cut the next patch release (1.0.2) within a week. So, if you have any patches that need to get into 1.0.2 make sure that either it is already in the 1.0.x branch or the corresponding ticket has

Re: Mesos CLI patches

Sorry, meant to send this to Haris directly. Please disregard. On Wed, Oct 5, 2016 at 1:19 PM Kevin Klues wrote: > Hey Haris, > > Now that the pods rush is over, we're finally ready to start pushing the > CLI patches through. Will you have time in the next few weeks to work

Re: Resource Isolation in Mesos

> These flags are used in agent - cgroups_limits_swap=true --isolation=cgroups/cpu,cgroups/mem --cgroups_hierachy=/sys/fs/c group In agent logs I can see updated memory limit to 33MB for container. Not sure if there are typos or not, some flags name may incorrect. Add according to >

Re: Troubleshooting tasks that are stuck in the 'Staging' state

> How do you typically monitor the messages between Master and Agents? For my side, I didn't monitor this. And only check the logs when troubleshooting some problems. Not sure if other users or developers have tools to meet your requirement here. On Wed, Oct 5, 2016 at 8:16 PM, Frank Scholten

Re: Resource Isolation in Mesos

What i can see in http output is mem_rss_bytes is not coming on rhel7. Here is the http output : Output for Agent running on rhel7 [{"container\_id":"8062e683\-204c\-40c2\-87ae\-fcc2c3f71b85","executor\_id":"\*\*\*\*\*","executor\_name":"Command Executor (Task: \*\*\*\*\*) (Command: sh \-c

Re: Troubleshooting tasks that are stuck in the 'Staging' state

Ok. How do you typically monitor the messages between Master and Agents? Do you have some tools for this on the cluster? On Tue, Oct 4, 2016 at 6:21 PM, haosdent wrote: > Hi, @Frank Thanks for your information > >> I see messages 'Telling agent (...) to kill task (...)'. Why

Re: Resource Isolation in Mesos

Hi, @Srikant How about the result of http://${YOUR_AGENT_IP}:5051/containers? It is wired that you could saw ``` Updated 'memory.limit_in_bytes' to xxx ``` in log as you mentioned, but `limit_in_bytes` is still the initialize value as you show above. On Wed, Oct 5, 2016 at 2:04 PM, Srikant

Re: Resource Isolation in Mesos

Here are the values - Memory.limit_in_bytes = 1107296256 Memory.soft_limit_in_bytes=1107296256 Memory.memsw.limit_in_bytes=9223372036854775807 I have run the same task on mesos 1.0.1 running on rhel6 and UI then shows task memory usage as 2.2G/1.0G where 2.2 is used and 1.0G is allocated but