Dan Carley

I thought that we had run into a startup/sync bug caused by this sleep but it actually turned out that the chart was using the wrong readiness endpoint: https://github.com/Kong/charts/pull/716

We use a sampling rate of 100% because we do dynamic sampling in [Refinery](https://docs.honeycomb.io/manage-data-volume/refinery/). We've been using this setup with 2.x in production mostly without problems since we added timeouts...

> @dcarley I'm curious in which cases the performance of the timer becomes bad. In 3.x we introduced [lua-resty-timer-ng](https://github.com/Kong/lua-resty-timer-ng) to reduce the overhead of the timer, and it shouldn't get...

> Hi @dcarley , could you please try 3.2.2 to check if this issue exists now? 3.2.2 appears to be worse than 3.0.1 for the reproduction case where `rate-limiting` "fails...

Cheers! I'll try to digest and test this when I'm back in the office next week.

Another use case for this is preventing the sensitive value of `-sealKey` from appearing in the process list for non-root users.

Thanks for testing the patch. I assume that I got a dependency error like this? ``` kong-3-1-0-kong-1 | ERROR: ./kong/globalpatches.lua:84: module 'resty.timerng' not found:No LuaRocks module found for resty.timerng ```...

Hi Samuel, Yeah, it is.

We didn't. The solution was to stop using RDS :wink: I'd still be interested in trying to fix this, though.

`.md` and `.markdown` don't work for me. `.text` (per issue #6) does work. ``` dan@dan-MBP ~ $ chromium-browser --version Chromium 18.0.1025.151 Built on Ubuntu 12.04, running on LinuxMint 13 ```