Apply fix for cgroups when used in docker containers

[tylersmalley]

A fix was made in Elasticsearch and elasticsearch-docker to workaround a mounting issue within cgroups. Logstash should account for this as well.

[tylersmalley]

cc: @bohyun-e

[bohyun-e]

@suyograo @ph could you guys look into this? Thanks.

[ph]

Thanks @bohyun-e

We have two solutions to implement the same workaround:

1. Either we add a new options to our logstash.yml file cgroups.hierarchy.override ?
2. Or we go with the java property option in the jvm.options file.

I am inclined to go to 1 route simply because we don't really use java properties.

[bohyun-e]

cc: @jasontedor since he's worked on the ES side of things.

[tylersmalley]

@ph, that's also the route were going to take in Kibana.

[jasontedor]

@tylersmalley @ph I recommend making two properties (instead of one as was done in Elasticsearch) and naming them something like cgroup.cpu.path.override and cgroup.cpuacct.path.override. I intend to deprecate cgroups.hierarchy.override in Elasticsearch and replace them with something like the above. Also, as we've done in Elasticsearch, I would make it clear that this a hack around an upstream problem and will eventually be removed.

[ph]

I've sync with @jasontedor and will use the following scheme:

cpu.cgroup.path.override
cpuacct.cgroup.path.override

[luismanuel001]

any workaround for this error?

[jayunit100]

were seeing this to, any update @ph

[shaunr88]

Was this work ever completed?

[antalm]

I'd like to run logstash in a container, but I don't want to mount /sys/fs/cgroup from the host. Is it possible to do so in recent version of logstash?