[GitHub] mesos issue #187: Add Zhongbo Tian to contributors.yaml.

[haosdent]

Github user haosdent commented on the issue:

https://github.com/apache/mesos/pull/187
  
LGTM 👍 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos issue #188: Add Douban to "Powered by Mesos" list.

[haosdent]

Github user haosdent commented on the issue:

https://github.com/apache/mesos/pull/188
  
LGTM, thank you.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos issue #188: Add Douban to "Powered by Mesos" list.

[windreamer]

Github user windreamer commented on the issue:

https://github.com/apache/mesos/pull/188
  
@haosdent is ths OK?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos pull request #188: Add Douban to "Powered by Mesos" list.

[windreamer]

GitHub user windreamer opened a pull request:

https://github.com/apache/mesos/pull/188

Add Douban to "Powered by Mesos" list.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/windreamer/mesos powered_by

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/mesos/pull/188.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #188


commit 3357d109f0c0daeb532aa040f5b532b472f2af9d
Author: tianzhongbo 
Date:   2016-11-22T07:25:01Z

Add Douban to "Powered by Mesos" list.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos issue #186: Update contributors.yaml

[windreamer]

Github user windreamer commented on the issue:

https://github.com/apache/mesos/pull/186
  
close in favor of #187 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos pull request #186: Update contributors.yaml

[windreamer]

Github user windreamer closed the pull request at:

https://github.com/apache/mesos/pull/186


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos pull request #187: Add Zhongbo Tian to contributors.yaml.

[windreamer]

GitHub user windreamer opened a pull request:

https://github.com/apache/mesos/pull/187

Add Zhongbo Tian to contributors.yaml.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/windreamer/mesos windreamer-path-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/mesos/pull/187.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #187


commit e8975566d7cac32ed54ac1cb53695c0df579b78f
Author: windreamer 
Date:   2016-11-22T07:04:28Z

Add Zhongbo Tian to contributors.yaml.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos issue #186: Update contributors.yaml

[windreamer]

Github user windreamer commented on the issue:

https://github.com/apache/mesos/pull/186
  
ok, did not notice it, sorry


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos issue #186: Update contributors.yaml

[haosdent]

Github user haosdent commented on the issue:

https://github.com/apache/mesos/pull/186
  
hi, @windreamer Since we order this list alphabetically, could you put your 
name before `name: zhou xing`?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos pull request #186: Update contributors.yaml

[windreamer]

GitHub user windreamer opened a pull request:

https://github.com/apache/mesos/pull/186

Update contributors.yaml



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/windreamer/mesos windreamer-patch-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/mesos/pull/186.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #186


commit 391cb31f70fe94f3d3ebb5b66788fde16383bd33
Author: windreamer 
Date:   2016-11-22T07:04:28Z

Update contributors.yaml




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Failed to launch spark jobs on mesos due to "hadoop" not found

[X Brick]

you can try "--executor_environment_variables" when you start mesos-slave
like the following:

```
/usr/local/sbin/mesos-agent --work_dir=/var/lib/mesos/agent  ...
--executor_environment_variables="{\"HADOOP_HOME\":\"/path/to/your/hadoop_home\"}"
```

Or you could patch MesosClusterScheduler.scala

and MesosCoarseGrainedSchedulerBackend.scala
,
set `HADOOP_HOME`, `JAVA_HOME` or something else dynamically, it will do
more hacking.

BTW, spark on mesos always switch user automatically, and if you did not
add user in the slave, may raise some errors. Set "--switch_user =false"
and env "HADOOP_USER_NAME" may be better.

2016-11-13 22:26 GMT+08:00 tommy xiao :

> let me input some hints information:
>
> for hadoop, you can see here about proxy_user concepts:
> https://hadoop.apache.org/docs/r2.7.1/hadoop-project-
> dist/hadoop-common/Superusers.html
>
> for lunch spark job in mesos cluster, see this case:
> https://marc.info/?l=mesos-user=144228174927503=3
>
>
>
>
>
> 2016-11-13 0:17 GMT+08:00 Yu Wei :
>
> > A little interesting.
> >
> >
> > 
> > From: tommy xiao 
> > Sent: Friday, November 11, 2016 2:19 PM
> > To: dev
> > Subject: Re: Failed to launch spark jobs on mesos due to "hadoop" not
> found
> >
> > this is pain. if the mesos support proxy user feature like hadoop,then
> > every thing can easy handle.
> >
> > 2016-11-11 14:06 GMT+08:00 Yu Wei :
> >
> > > I fixed the problem by adding environment variables HADOOP_HOME and
> > > JAVA_HOME to launch mesos-agent as below,
> > >
> > > sudo HADOOP_HOME=/home/dcos/repo/bigdata/hadoop-2.7.3/
> > > JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.111-1.b15.
> > el7_2.x86_64/jre/
> > > /usr/local/sbin/mesos-agent --work_dir=/var/lib/mesos/agent  ...
> > >
> > > It seemed that this is caused by sudo secure_path.
> > >
> > >
> > > Is there any better solution to fix this problem?
> > >
> > >
> > >
> > > Thanks,
> > >
> > > Jared, (??)
> > > Software developer
> > > Interested in open source software, big data, Linux
> > >
> > > 
> > > From: tommy xiao 
> > > Sent: Friday, November 11, 2016 1:52:54 PM
> > > To: dev
> > > Subject: Re: Failed to launch spark jobs on mesos due to "hadoop" not
> > found
> > >
> > > it seem like in same user mode.
> > >
> > > 2016-11-10 22:37 GMT+08:00 Joris Van Remoortere :
> > >
> > > > Switch to the user that the agent is running as, and the directory
> from
> > > > which it is executing and ensure that you can find hadoop. For
> example
> > by
> > > > running
> > > > `which hadoop`. This may be a PATH or JAVA_HOME issue?
> > > >
> > > > -
> > > > *Joris Van Remoortere*
> > > > Mesosphere
> > > >
> > > > On Thu, Nov 10, 2016 at 6:29 AM, Yu Wei  wrote:
> > > >
> > > > > Hi Guys,
> > > > >
> > > > > I failed to launch spark jobs on mesos. Actually I submitted the
> job
> > to
> > > > > cluster successfully.
> > > > >
> > > > > But the job failed to run.
> > > > >
> > > > > I1110 18:25:11.095507   301 fetcher.cpp:498] Fetcher Info:
> > > > > {"cache_directory":"\/tmp\/mesos\/fetch\/slaves\/
> > > > 1f8e621b-3cbf-4b86-a1c1-
> > > > > 9e2cf77265ee-S7\/root","items":[{"action":"BYPASS_CACHE","
> > > > > uri":{"extract":true,"value":"hdfs:\/\/192.168.111.74:9090\/
> > > > > bigdata\/package\/spark-examples_2.11-2.0.1.jar"}}],"
> > > > > sandbox_directory":"\/var\/lib\/mesos\/agent\/slaves\/
> > > > > 1f8e621b-3cbf-4b86-a1c1-9e2cf77265ee-S7\/frameworks\/
> > > > > 1f8e621b-3cbf-4b86-a1c1-9e2cf77265ee-0002\/executors\/
> > > > > driver-20161110182510-0001\/runs\/b561328e-9110-4583-b740-
> > > > > 98f9653e7fc2","user":"root"}
> > > > > I1110 18:25:11.099799   301 fetcher.cpp:409] Fetching URI 'hdfs://
> > > > > 192.168.111.74:9090/bigdata/package/spark-examples_2.11-2.0.1.jar'
> > > > > I1110 18:25:11.099820   301 fetcher.cpp:250] Fetching directly into
> > the
> > > > > sandbox directory
> > > > > I1110 18:25:11.099862   301 fetcher.cpp:187] Fetching URI 'hdfs://
> > > > > 192.168.111.74:9090/bigdata/package/spark-examples_2.11-2.0.1.jar'
> > > > > E1110 18:25:11.101842   301 shell.hpp:106] Command 'hadoop version
> > > 2>&1'
> > > > > failed; this is the output:
> > > > > sh: hadoop: command not found
> > > > > Failed to fetch 'hdfs://192.168.111.74:9090/bigdata/package/spark-
> > > > > examples_2.11-2.0.1.jar': Failed to create HDFS client: Failed to
> > > execute
> > > > > 'hadoop version 2>&1'; the command was either not found or exited
> > with
> > > a
> > > > > non-zero exit status: 127
> > 

[GitHub] mesos issue #179: Added a new title to the existing list

[packtpartner]

Github user packtpartner commented on the issue:

https://github.com/apache/mesos/pull/179
  
Thank you @bmahler 
Sorry for the trouble.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos issue #185: Added DNT to Powered by Mesos list.

[gyliu513]

Github user gyliu513 commented on the issue:

https://github.com/apache/mesos/pull/185
  
cc @bmahler 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos pull request #185: Added DNT to Powered by Mesos list.

[shisy]

GitHub user shisy opened a pull request:

https://github.com/apache/mesos/pull/185

Added DNT to Powered by Mesos list.

We have a D-DCOS based on Mesos and want to be listed by Powered
by Mesos list.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/shisy/mesos master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/mesos/pull/185.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #185


commit 09fec84c50ba932b5903395cbe254b445d86b96b
Author: Shisy 
Date:   2016-11-22T02:41:27Z

Added DNT to Powered by Mesos list.

We have a D-DCOS based on Mesos and want to be listed by Powered
by Mesos list.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos pull request #181: Add elastic-job -cloud description into frameworks....

[bmahler]

Github user bmahler commented on a diff in the pull request:

https://github.com/apache/mesos/pull/181#discussion_r89031974
  
--- Diff: docs/frameworks.md ---
@@ -30,6 +30,7 @@ layout: documentation
 
 * [Chronos](https://github.com/mesos/chronos) is a distributed job 
scheduler that supports complex job topologies. It can be used as a more 
fault-tolerant replacement for Cron.
 * [Cook](https://github.com/twosigma/cook) is a job scheduler like Torque 
that not only supports individual tasks, but also Spark. Cook provides powerful 
automatic preemption and multitenancy features for shared clusters, in order to 
guarantee throughput to all users while allowing individuals to temporarily 
"burst" to additional resources as needed. Cook provides a simple REST API & 
Java client for interaction.
+* [Elastic-Job-Cloud](https://github.com/dangdangdotcom/elastic-job) is a 
distributed scheduled job cloud solution. It focus on scale out, 
fault-tolerant(failover, misfire), flexible job scenarios(transient, daemon), 
complex trigger(cron, event driven), extra job templates(dataflow), jobs 
running history trace.
--- End diff --

How about "is a distributed scheduled job cloud solution designed with HA 
and fault-tolerance in mind. It focuses on horizontal scaling, and provides 
transient and daemon jobs, event and schedule based job triggers, job 
dependencies, and job history."

I tried to rephrase this a bit, does it still sound accurate?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos issue #179: Added a new title to the existing list

[bmahler]

Github user bmahler commented on the issue:

https://github.com/apache/mesos/pull/179
  
I pushed this with some minor changes to make it consistent with the other 
entries.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos pull request #179: Added a new title to the existing list

[bmahler]

Github user bmahler commented on a diff in the pull request:

https://github.com/apache/mesos/pull/179#discussion_r89031027
  
--- Diff: docs/home.md ---
@@ -109,6 +109,11 @@ layout: documentation
 
 
   
+https://www.packtpub.com/big-data-and-business-intelligence/mastering-mesos;
 class="thumbnail">
+  https://www.packtpub.com/sites/default/files/6249OS_5186%20Mastering%20Mesos.jpg;
 alt="Mastering Mesos by Dipa Dubhashi and Akhil Das">
+
+
--- End diff --

Also it looks like you don't want to open a new class=row div here. You're 
missing the title text as well. If you have a look at the other entries you can 
see the expected format.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos pull request #179: Added a new title to the existing list

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/mesos/pull/179


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos pull request #183: Add PyMesos in api-client-libraries.md

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/mesos/pull/183


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos pull request #179: Added a new title to the existing list

[bmahler]

Github user bmahler commented on a diff in the pull request:

https://github.com/apache/mesos/pull/179#discussion_r89030359
  
--- Diff: docs/home.md ---
@@ -109,6 +109,11 @@ layout: documentation
 
 
   
+https://www.packtpub.com/big-data-and-business-intelligence/mastering-mesos;
 class="thumbnail">
--- End diff --

I think the current ordering is alphabetical based on the name of the 
title, can you place this after "Building Applications..." and before "Mesos in 
Action..."?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos pull request #184: In CentOS 7, the libevent-devel dependency is neede...

[chjhaijiang]

Github user chjhaijiang closed the pull request at:

https://github.com/apache/mesos/pull/184


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos pull request #182: Add TFMesos in frameworks.md

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/mesos/pull/182


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos issue #182: Add TFMesos in frameworks.md

[xiaods]

Github user xiaods commented on the issue:

https://github.com/apache/mesos/pull/182
  
+1


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos issue #184: In CentOS 7, the libevent-devel dependency is needed to be...

[xiaods]

Github user xiaods commented on the issue:

https://github.com/apache/mesos/pull/184
  
OMG, it is need rebase.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos pull request #184: In CentOS 7, the libevent-devel dependency is neede...

[chjhaijiang]

GitHub user chjhaijiang opened a pull request:

https://github.com/apache/mesos/pull/184

In CentOS 7, the libevent-devel dependency is needed to be installed for 
mesos SSL build.

In  the link 
(https://github.com/apache/mesos/blob/master/docs/getting-started.md), it 
should be a proper instruction once user want to build a SSL mesos. Right now, 
it is missed. 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/apache/mesos master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/mesos/pull/184.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #184


commit 97bd957ffc45b3484dd82321c5e7fe7f02f9d79c
Author: Neil Conway 
Date:   2016-10-19T23:32:14Z

Changed master to send TASK_UNKNOWN during reconciliation.

Previously, the master would send TASK_LOST in response to explicit
reconciliation requests for (a) unknown tasks at registered slaves and
(b) tasks at unknown slaves (neither registered nor unreachable). The
master will now send TASK_UNKNOWN for these situations if the framework
has the PARTITION_AWARE capability.

Review: https://reviews.apache.org/r/52693/

commit da2ca0f17d9ac9a0248edd18ed2cc7c774e985d4
Author: Neil Conway 
Date:   2016-10-19T23:32:21Z

Renamed a function for clarity.

`Master::reconcile(Framework*, const scheduler::Call::Reconcile&)` and
`Master::reconcile(Slave*, const vector&, const
vector& tasks)` are only loosely related. Per discussion on the
development list, using overloading to distinguish these two functions
is confusing. Hence, rename the latter to `reconcileKnownSlave`.

Review: https://reviews.apache.org/r/52719/

commit bf00061b5dd2d5552ad14a206cf8167b70d669c3
Author: Neil Conway 
Date:   2016-10-19T23:32:27Z

Clarified a comment.

Review: https://reviews.apache.org/r/52720/

commit e65b40d48b25ecf45805c8a740a412074da00d1f
Author: Megha Sharma 
Date:   2016-10-20T00:34:19Z

Fixed a bug that causes the fetcher to not chown the sandbox.

Moved the `uri.size() == 0` check in fetcher so that the chown to
task user of stdout/stderr in sandbox directory happens even when
there is no uri to be fetched.

Review: https://reviews.apache.org/r/52828/

commit 09a1cd10278992360c63a77d2712b9d047ce0e67
Author: Megha Sharma 
Date:   2016-10-20T00:37:16Z

Fixed fetcher to not recursively chown the entire sandbox.

Fetcher currently changes the ownership of entire sandbox directory
recursively to the task user and as a result also changes the
ownership of files laid down by other entities in the sandbox, which
leads to unintended side-effects.

Review: https://reviews.apache.org/r/52058/

commit 6880a5f6c82aa5b535ebe2f1b86bad5ca338cb15
Author: Santhosh Kumar Shanmugham 
Date:   2016-10-20T15:54:52Z

Close socket after setting flags on the interface.

Review: https://reviews.apache.org/r/53049/

commit d46807a1c672989b70a33c1fc9355b0bee3855fd
Author: haosdent huang 
Date:   2016-10-20T17:41:14Z

Added non-recursive version of `cgroups::get`.

In most cases, we just want to get the children cgroups instead of
retrieve descendant cgroups recursively. We added an argument to
`cgroups::get` to indicate whether to retrieve cgroups recursively and
made non-recursive retrieve the default behaviour. This patch fixed
some incorrect `TEST_CGROUPS_ROOT` checks as well.

Review: https://reviews.apache.org/r/51031/

commit 4c25f17d87a098a4eb0815156447730cc6111942
Author: haosdent huang 
Date:   2016-10-20T17:44:11Z

Removed the expired TODO about non-recursive version `cgroups::get`.

Review: https://reviews.apache.org/r/51185/

commit fcdc547d720cbb962ec2e498a70fbadd3cf75397
Author: Anindya Sinha 
Date:   2016-10-20T18:05:37Z

Treat failure in destroy of non-existing nested cgroups as a success.

This may happen if certain daemon on the host creates and deletes
nested cgroups inside Mesos containers but the nested cgroups are not
managed by Mesos; we shouldn't fail the destroy. Ultimately the
rationale for this change is that if the goal is to destroy a cgroup
and the end result is that it's gone, then we should consider it a
success even though some nested cgroups are cleaned up out-of-band
by other entities.

Review: https://reviews.apache.org/r/53031/

commit 78d4ec406f7bee61eb5097bca91bf143d2f43f82
Author: Joris Van Remoortere 
Date:   2016-10-18T22:33:09Z

Removed extra 'evolve' implementation from