[SERVER-12975] Write command to mongos with invalid NS fails differently with mixed versions Created: 28/Feb/14 Updated: 11/Jul/16 Resolved: 10/Mar/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding, Write Ops |
| Affects Version/s: | 2.6.0-rc0 |
| Fix Version/s: | 2.6.0-rc2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Siyuan Zhou |
| Resolution: | Done | Votes: | 0 |
| Labels: | 26qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
Filing as a bug since greg_10gen thinks this should be caught by mongos before forwarding command to shards. Collection name is "unsharded.errors.$foo". As the db name implies, this is to an unsharded DB. 2.6 mongos with 2.6 shards:
2.6 mongos with 2.4 shards:
|
| Comments |
| Comment by Githook User [ 10/Mar/14 ] |
|
Author: {u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'}Message: |
| Comment by Mathias Stearn [ 28/Feb/14 ] |
|
Added info about collection to Description field. |
| Comment by Greg Studer [ 28/Feb/14 ] |
|
The collection name itself would be useful here - it'll narrow down the validation that's not happening. |