Ryan Eschinger
Ryan Eschinger
to this effectively, we also need to be able to do a lookup on map fields.
I added some ideas there
Yes, mesos is running with `--isolation=cgroups/cpu,cgroups/mem` and can confirm that memory limits are being enforced on other (non-docker) tasks running in mesos.
it looks like the elasticsearch java processes are launched outside of the cgroup that has the memory limit applied: ``` shell root 7407 0.0 0.0 115244 1484 ? Ss 12:48...
I'd be glad to but I am unable to build the project (either on master or the 1.0.1 tag) following the instructions at http://mesos-elasticsearch.readthedocs.io/en/latest/. I get various scheduler test failures....
I was able to build the image but, unfortunately, using `exec` doesn't seem to resolve the problem. the java processes still run outside the parent `mesos-executor` cgroup. I tried a...
Sounds good. The updated README definitely clarifies things. Thanks!
in order to configure hdfs for our platform, we currently have to build a custom hdfs scheduler package: https://github.com/CiscoCloud/mantl-hdfs. it would be wonderful if we eventually didn't have to maintain...
Sorry, I am not able to reproduce this. Do you have any other terraform files in your directory that defines outputs with those names?
note this affects, at minimum, #346, #355, and #334 (just the elk example part of it)