[SERVER-17964] sharding_jscore_passthrough.js test should only start with one shard Created: 09/Apr/15 Updated: 19/Sep/15 Resolved: 10/Apr/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Sharding 2 04/24/15 |
| Participants: |
| Description |
|
Currently, the sharding_jscore_passthrough.js shim starts two shards. This causes some commands, which depend on the same shard being picked up every time to fail. One example is rename collection across databases. It would be best if this test is made to only start a single shard. |
| Comments |
| Comment by Githook User [ 10/Apr/15 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |