[SERVER-12820] copydb fails via mongos Created: 21/Feb/14 Updated: 11/Jul/16 Resolved: 11/Mar/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.6.0-rc0 |
| Fix Version/s: | 2.6.0-rc2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | A. Jesse Jiryu Davis | Assignee: | Shaun Verch |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Major Change | |||||||||||||||||||||||||||
| Operating System: | ALL | |||||||||||||||||||||||||||
| Steps To Reproduce: | Set up a sharded cluster of two replica sets, and call copydb on mongos:
With mongod 2.4.9, the database is copied and copydb returns "ok": 1. With mongod
The fault seems to be mongod's, since copydb works with old |
|||||||||||||||||||||||||||
| Participants: |
| Description |
|
"copydb" from mongos fails if the shards are replica sets running latest mongod. |
| Comments |
| Comment by Githook User [ 11/Mar/14 ] |
|
Author: {u'username': u'Zarkantho', u'name': u'Shaun Verch', u'email': u'shaun.verch@10gen.com'}Message: |
| Comment by Githook User [ 11/Mar/14 ] |
|
Author: {u'username': u'Zarkantho', u'name': u'Shaun Verch', u'email': u'shaun.verch@10gen.com'}Message: |
| Comment by Githook User [ 05/Mar/14 ] |
|
Author: {u'username': u'monkey101', u'name': u'Dan Pasette', u'email': u'dan@10gen.com'}Message: Revert " This reverts commit db6f4c6227581996ecba987be21912ed0824592c. |
| Comment by Githook User [ 04/Mar/14 ] |
|
Author: {u'username': u'Zarkantho', u'name': u'Shaun Verch', u'email': u'shaun.verch@10gen.com'}Message: |