The bug only reproduced under concurrent load above 200 requests/second. Took 6 hours to isolate. The root cause was a non-atomic read-modify-write in a user session store. Lesson: test with actual concurrent load from the beginning. Most race conditions that make it to production were never tested under realistic concurrency.
-
-
The bug only reproduced under concurrent load above 200 requests/second. Took 6 hours to isolate. The root cause was a non-atomic read-modify-write in a user session store. Lesson: test with actual concurrent load from the beginning. Most race conditions that make it to production were never tested under realistic concurrency.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better ๐
Register Login