[SERVER-24792] Ensure that mongos from 3.4 will refuse to talk to mongod from 3.2 Created: 24/Jun/16 Updated: 19/Nov/16 Resolved: 20/Sep/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.14 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Nathan Myers |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Sharding 18 (08/05/16), Sharding 2016-08-29, Sharding 2016-09-19, Sharding 2016-10-10 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||
| Comments |
| Comment by Githook User [ 20/Sep/16 ] |
|
Author: {u'name': u'Nathan Myers', u'email': u'ncm@asperasoft.com'}Message: |
| Comment by Githook User [ 20/Sep/16 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: Revert " This reverts commit dc405959d785dc1f50682877d732da0124e4b3b2. |
| Comment by Githook User [ 20/Sep/16 ] |
|
Author: {u'name': u'Nathan Myers', u'email': u'ncm@asperasoft.com'}Message: |
| Comment by Nathan Myers [ 15/Sep/16 ] |
|
Changes are at https://github.com/nathan-myers-mongo/mongo/tree/server-24792-no-connect-old |
| Comment by Esha Maharishi (Inactive) [ 08/Sep/16 ] |
|
Additional note: write operations (insert, update, remove) will show the failure as part of writeErrors, not as part of the top-level command error. nathan.myers, you might want to user assert.writeError() for the write operations instead of assert.commandFailed() (the attached script currently uses assert.commandFailed() incorrectly). |
| Comment by Esha Maharishi (Inactive) [ 08/Sep/16 ] |
|
At a minimum, the following commands should be tested:
schwerin, I agree it would make sense to put this in jstests/multiVersion. |
| Comment by Andy Schwerin [ 24/Jun/16 ] |
|
Is there an existing multiversion test, or should we add one, as well? |