[SERVER-1445] jstests/shellkillop.js fails in a sharded setup Created: 19/Jul/10 Updated: 28/Nov/17 Resolved: 16/Sep/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding, Testing Infrastructure |
| Affects Version/s: | 1.5.5 |
| Fix Version/s: | 3.1.9 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Richard Kreuter (Inactive) | Assignee: | YunHe Wang |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Quint 9 09/18/15 | ||||||||
| Participants: | |||||||||
| Case: | (copied to CRM) | ||||||||
| Description |
|
jstests/shellkillop.js fails in a sharded setup. Shell cant kill ops forwarded by mongos on ctrl-c. client field in currentOp() is for mongos -> mongod link, not for client -> mongos link, therefore it won't match the output of whatsmyuri. |
| Comments |
| Comment by Githook User [ 16/Sep/15 ] |
|
Author: {u'username': u'yhjw88', u'name': u'Yunhe (John) Wang', u'email': u'yunhe.wang@mongodb.com'}Message: |
| Comment by YunHe Wang [ 14/Sep/15 ] |
|
The test jstests/core/shellkillop.js now works in sharding_jscore_passthrough as of 3.1. |