Interleaved/Partial log output

[mikehale]

To be fair I'm not certain if this is a scrolls issue or something related to the heroku logging infrastructure. I have seen it on a platform app and a bare metal app using unicorn.

Example output:

2012-10-15T14:25:59+00:00 app[web.15]: fn=submit_to_librato at=error 
2012-10-15T14:26:41+00:00 app[web.39]: fn=submit_to_librato at=error exception="metric 
2012-10-15T14:27:46+00:00 app[web.17]: fn=submit_to_librato at=error exceptio
2012-10-15T14:28:21+00:00 app[web.15]: fn=submit_to_librato at=error exce
2012-10-15T14:28:47+00:00 app[web.1]: fn=submit_to_librato at=error excepti
2012-10-15T14:29:42+00:00 app[web.29]: fn=submit_to_librato at=error exception="met
2012-10-15T14:29:44+00:00 app[web.20]: fn=submit_to_librato at=error except

I would expect to see something like:

2012-10-15T14:29:42+00:00 app[web.29]: fn=submit_to_librato at=error exception="metric too old"

[mikehale]

/cc @pedro

[pedro]

Oh man, +1. This has been haunting us for quite a while - latest attempt was to reset the Scrolls Mutex on Unicorn fork but that didn't seem to improve the situation.

@mikehale do you have more info on the apps that had this issue? Are they 1.8.7? Unicorn?

[mikehale]

I was seeing it on an heroku/backstop, which uses thin, ruby 1.9.2, and sinatra.

[asenchi]

I'll be honest I have no idea how to reproduce this. I never saw it while I was at Heroku and I haven't put Scrolls through any rigorous logging at GitHub.

If you find something let me know.

[asenchi]

Going to close this due to not enough information. If you see it again, let's reopen and see if we can reproduce.