[SERVER-8451] Mongo shell can theoretically kill wrong op Created: 06/Feb/13  Updated: 15/Feb/13  Resolved: 06/Feb/13

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Question Priority: Minor - P4
Reporter: Hannes Magnusson Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

The word on the street is that the mongo shell keeps track of its current connection id.
When you hit ctrl+c to abort the current operation it will reconnect to the server, list out the current operations, grep for the previous connection id and kill the operation.

If that is correct, then.. since we recycle connection ids - we could potentially be killing incorrect operation if there are many enough connections to the server being made!



 Comments   
Comment by Eliot Horowitz (Inactive) [ 06/Feb/13 ]

Its ip + port, and we get the op id before we kill the socket, so should be impossible for it to kill someone else's op.

Generated at Thu Feb 08 03:17:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.