[SERVER-2173] kill connection on server WAS: Method to view queued jobs and purge the queue Created: 02/Dec/10 Updated: 10/Dec/14 Resolved: 16/Jan/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | David Mytton | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
If you issue many remove() queries, they're not executed all at once but are queued up. There's no way to see the queue and purge it (other than bouncing the mongos). |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 16/Jan/14 ] |
|
The old op codes that caused this behavior are being deprecated, new ones don't have these symptoms. |
| Comment by Eliot Horowitz (Inactive) [ 02/Dec/10 ] |
|
There isn't really a queue per se, its just the tcp pipe. We could offer a kill connection option though. |