Thanks Scott I just needed a bit of confirmation.
And yes it's quite impressive and a bit scary that a single second could create problem on the scale we've seen - and judging by what we've seen so far this will most likely not be the last time a leap second gets this much attention. Lets just hope the next one doesn't happen on december 31st - I'd hate to have to use my reduced mental capacity on january 1st (seems to be a recurring issue on that date) on fixing crashed systems.. ;) Regards, Jens Dueholm Christensen Survey IT From: resin-interest-boun...@caucho.com [mailto:resin-interest-boun...@caucho.com] On Behalf Of Scott Ferguson Sent: Monday, July 02, 2012 9:25 PM To: resin-interest@caucho.com Subject: Re: [Resin-interest] Leap Second behaviour On 07/02/2012 06:28 AM, Jens Dueholm Christensen (JEDC) wrote: Hi I'm quite well aware that the "base problem" regarding leap seconds is not connected to Resin, but to JVM and OS. However I saw some strange behaviour in the aftermatch, that might be interesting to clear up. Normally we run Resin 3.1.12 without any specific configuration for <stat-service>. This means a default sample-period of 60 seconds. Because of this every 59th second this was logged: [2012-07-01 02:14:59.000][02:14:59.000] StatService[] cpu-load=41.05 [2012-07-01 02:14:59.000][02:14:59.000] StatService[] cpu-load=41.05 [2012-07-01 02:14:59.000][02:14:59.000] StatService[] cpu-load=41.05 [2012-07-01 02:14:59.000][02:14:59.000] StatService[] cpu-load=41.05 [2012-07-01 02:14:59.000][02:14:59.000] StatService[] cpu-load=41.05 ... ~26600 lines later [2012-07-01 02:14:59.999][02:14:59.999] StatService[] cpu-load=41.05 [2012-07-01 02:14:59.999][02:14:59.999] StatService[] cpu-load=41.05 [2012-07-01 02:14:59.999][02:14:59.999] StatService[] cpu-load=41.05 [2012-07-01 02:14:59.999][02:14:59.999] StatService[] cpu-load=41.05 [2012-07-01 02:14:59.999][02:14:59.999] StatService[] cpu-load=41.05 [2012-07-01 02:14:59.999][02:14:59.999] StatService[] cpu-load=41.05 [2012-07-01 02:14:59.999][02:14:59.999] StatService[] cpu-load=41.05 This seemed a bit much to log every 60th second. I tried to add a <stat-service> section with 10 minute sample-period, and saw that those ~26600 lines was now only logged every 10th minute. But still loads more than usual (I would expect just a single line beeing logged). Was Resin to blame for this (ie. is there a possible bug around here?) or was it the JVM and OS? I'd guess it's related to the JVM/OS issue. In our nightly regressions, there were some sleep/waits that were stuck before we updated the system. It's pretty impressive that a 1s change could cause that much chaos. :) -- Scott Regards, Jens Dueholm Christensen Survey IT _______________________________________________ resin-interest mailing list resin-interest@caucho.com<mailto:resin-interest@caucho.com> http://maillist.caucho.com/mailman/listinfo/resin-interest
_______________________________________________ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
