+Steve
On Wed, Nov 30, 2016 at 5:40 PM, Piotr Szczesniak
wrote:
> Hi Steve,
>
> Your use case is out of the scope of Heapster project, which is about
> gathering system metrics (like resource usage) rather than a part of
> alerting pipeline. Added a few folks from Stackdriver which can elaborate
On Wednesday, November 30, 2016 at 2:23:16 PM UTC-8, kvch...@gmail.com wrote:
> Here is why?
> root@ovrh0301:/home/envi# ulimit -a
> core file size (blocks, -c) 0
> data seg size (kbytes, -d) unlimited
> scheduling priority (-e) 0
> file size (blocks, -f
SIG On-Prem was one of the initial namings of the SIG when the new SIG
discussion had been initiated. I've upvoted this naming and absolutely will
do it now.
The only note that I have - we have SIG-OpenStack, that covers the on-prem
solutions as well. - we have to find the way how our [overlapping
No, it doesn't. We `ulimit -n 10240` in our start script and it works just
fine.
Where do you set the raised limit? Apparently upstart ignores limits.conf
and you need to set this in your job definition:
http://bryanmarty.com/2012/02/10/setting-nofile-limit-upstart/
/MR
On Wed, Nov 30, 2016 at
