another piece of (potentially useful) information is that the I have haproxy load balancing to 3 different machines with appservers (one of them being the same machine running haproxy). the corruption only occured when balancing to the 2 appservers on separate machines and never seemed to affect the local appservers.
On Sun, Apr 19, 2009 at 9:03 PM, Arash Ferdowsi <[email protected]> wrote: > hi all, > I'v been happily using 1.3.15.7 (sitting behind nginx) with no real > problems to report of. I tried out 1.3.17 and ran into a fairly > strange and serious problem. > > I had the new version running in production for about an hour (served > about 800k requests in this period). after a few minutes of production > load, requests from several clients were failing in some application > level assertions (the post variable in question is base64 decoded and > then zlib decompressed). it's difficult for me to tell exactly what's > being corrupted in the request body, but I have noticed that it > generally seems to happen twice per IP (the client generally retries > 30 seconds after a failure) and the same assertion will trigger the > next time around. the bodies from back-to-back requests are supposed > to be identical (and are in length) but not in content. > > have any similar issues been reported on 1.3.17? what can I do to help > debug this? thanks in advance :-). > > > -- > Arash Ferdowsi > CTO, Dropbox > 913.707.5875 (m) > -- Arash Ferdowsi CTO, Dropbox 913.707.5875 (m)
