[SERVER-723] access current ops isn't thread safe Created: 09/Mar/10 Updated: 12/Jul/16 Resolved: 29/Jul/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency |
| Affects Version/s: | 1.3.3 |
| Fix Version/s: | 1.5.7 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Kyle Banker | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
To reproduce, start a long-running script that inserts large documents into a collection. Then run: ab -n10000 -c2 http://127.0.0.1:28017/ You'll get assertions like these. Not sure how to explain this, but it's definitely triggered by hitting the web server. Tue Mar 9 11:30:34 MiniWebServer: connection accepted from 127.0.0.1:64941 |
| Comments |
| Comment by auto [ 29/Jul/10 ] |
|
Author: {'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}Message: use checksum to make curop threadsafe |
| Comment by beawesomeinstead [ 10/Mar/10 ] |
|
Here's an example rake task that relies on mongo_ext, mongo_mapper and ccsv. |