[JAVA-1109] Allow killing of ops Created: 12/Feb/14 Updated: 27/May/22 Resolved: 08/Dec/17 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Monitoring |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Charlie Page | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 5 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Server Compat: | 4.1 | ||||||||
| Description |
|
Allow operations to be killed. A connection should have a handle that allows an operation running on that connection to be asynchronously killed. |
| Comments |
| Comment by Jeffrey Yemin [ 08/Dec/17 ] |
|
Now that the driver supports sessions, operations can be killed based on the session identifier. |
| Comment by Scott Hernandez (Inactive) [ 11/Sep/14 ] |
|
The shell can kill all active operations by connection by use "whatsMyUri", currentOp, and kill by id based on filter that info by client uri. Also noted here |
| Comment by Jeffrey Yemin [ 13/Mar/14 ] |
|
The new support for maxTimeMS may be of interest. |