[SERVER-22217] Remove large number of document will block the bulkOperation Created: 18/Jan/16 Updated: 14/Apr/16 Resolved: 18/Jan/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | gabriel.wang | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | feature, legacy-cxx | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
MongoDB version: 3.0.5 |
||
| Participants: |
| Description |
|
When removing 23387 documents from the collection which has 250K documents), The BulkOperation was block until the remove is done. Following is the log regarding the remove operation. 2016-01-17T00:05:05.965-0500 I WRITE [conn1] remove xxx.app query: { app.start_time: { $lt: new Date(1453003200000), $lt: new Date(1453003200000) }} ndeleted:23387 keyUpdates:0 writeConflicts:0 numYields:194 locks:{ Global: { acquireCount: { r: 195, w: 195 }}, Database: { acquireCount: { w: 195 }}, Collection: { acquireCount: { w: 195 } } } 2630ms }, limit: 0 } ], ordered: true, writeConcern: {} } keyUpdates:0 writeConflicts:0 numYields:0 reslen:40 locks:{ Global: { acquireCount: { r: 196, w: 196 }}, Database: { acquireCount: { w: 196 }}, Collection: { acquireCount: { w: 196 }} } 2639ms Size BulkOperation: 100 operations per BulkOperationBuilder. Is there a way to make the bulkOperation and remove running concurrently. |
| Comments |
| Comment by Stennie Steneker (Inactive) [ 18/Jan/16 ] |
|
Hi Gabriel, Thanks for your question. Please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. If you find a bug or have a feature you'd like to see in the MongoDB server please feel free to open new tickets here. For MongoDB-related support discussion you can post on the mongodb-user group or Stack Overflow with the mongodb tag, where your questions will reach a large audience of MongoDB users, developers and enthusiasts. A question like this involving more discussion would be best posted on the mongodb-user group. Regards, |