[SERVER-6042] Check for remaining Windows issues in shell multithreading with V8 Created: 08/Jun/12 Updated: 28/Apr/17 Resolved: 28/Apr/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | JavaScript, Shell |
| Affects Version/s: | 2.1.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tad Marshall | Assignee: | DO NOT USE - Backlog - Platform Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | Windows | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows with V8 |
||
| Issue Links: |
|
||||||||||||
| Operating System: | Windows | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
We did work for 2.1.2 to make sure that the Mongo shell was thread-safe when multi-threading JavaScript under V8 in the Linux version. This ticket is to make sure that this also works correctly in Windows when built with V8. |
| Comments |
| Comment by Andrew Morrow (Inactive) [ 28/Apr/17 ] |
|
Since MongoDB 3.2, mongod no longer uses the V8 Javascript engine. |
| Comment by Eric Milkie [ 21/Feb/13 ] |
|
Further work pushed to 2.5 |
| Comment by Tad Marshall [ 21/Feb/13 ] |
|
I'd like to see manyclients.js stop leaving zombie threads in Windows 64-bit when run with threads=200. This test never finishes with threads=200; it does finish with threads=50 and I'd like to understand what is going on there, especially since it passes with threads=200 on Linux 64-bit. It's OK with me to reschedule this for 2.5 since it isn't affecting anything that we know of other than this test (and the test now uses threads=50 and passes). |
| Comment by Eric Milkie [ 20/Feb/13 ] |
|
What is left to do, if anything, for this? |
| Comment by Tad Marshall [ 08/Jun/12 ] |
|
Linking to Linux version of ticket. |