[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. 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. |