[SERVER-18292] Re-enable all tests tagged with SERVER-18292 Created: 01/May/15 Updated: 06/Dec/17 Resolved: 28/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.10 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Adam Midvidy | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Sprint: | Platform 4 06/05/15, Platform 5 06/26/16, Repl 2017-05-08, Repl 2017-05-29, Repl 2017-06-19, Repl 2017-07-10 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Some tests were disabled pending implementation of OP_COMMAND in mongos. Since we have decided not to do that and instead use OP_MSG in both mongos and mongod, we need to ensure that the disabled tests are re-enabled. Original title and description:Implement OP_COMMAND in mongos Depends on the metadata refactor as that will make it very simple to upconvert/downconvert between different message types. This will include implementing autodetection of support for OP_COMMAND in the C++ driver, and multiversion testing. |
| Comments |
| Comment by Githook User [ 28/Jun/17 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: |
| Comment by Githook User [ 28/Jun/17 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: |
| Comment by Robert Guo (Inactive) [ 10/Sep/15 ] |
|
adam.midvidy There's a comment in the sharding jscore passthrough suite to remove invalid_db_name.js and validate_cmd_ns.js from the exclusion list once this ticket is done. I tried it in a recent build but both tests seem to be failing. Reading the comments in this ticket, it looks like some of the functionality was cut, so should the comment in the yml file be updated? |
| Comment by Githook User [ 16/Jun/15 ] |
|
Author: {u'username': u'amidvidy', u'name': u'Adam Midvidy', u'email': u'amidvidy@gmail.com'}Message: |
| Comment by Githook User [ 16/Jun/15 ] |
|
Author: {u'username': u'amidvidy', u'name': u'Adam Midvidy', u'email': u'amidvidy@gmail.com'}Message: |
| Comment by Githook User [ 16/Jun/15 ] |
|
Author: {u'username': u'amidvidy', u'name': u'Adam Midvidy', u'email': u'amidvidy@gmail.com'}Message: |
| Comment by Githook User [ 16/Jun/15 ] |
|
Author: {u'username': u'amidvidy', u'name': u'Adam Midvidy', u'email': u'amidvidy@gmail.com'}Message: |
| Comment by Githook User [ 16/Jun/15 ] |
|
Author: {u'username': u'amidvidy', u'name': u'Adam Midvidy', u'email': u'amidvidy@gmail.com'}Message: |
| Comment by Githook User [ 16/Jun/15 ] |
|
Author: {u'username': u'amidvidy', u'name': u'Adam Midvidy', u'email': u'amidvidy@gmail.com'}Message: |
| Comment by Kaloian Manassiev [ 08/Jun/15 ] |
|
Unfortunately we have no plans of removing either of those abstractions for 3.2. 1 cannot be done and not point in doing it for 3.2 when we can just get rid of the entire LCM in 3.4 I think these should remain as they are in 3.2 (given that we have compatiblity support) and then most of them will go away in 3.4. |
| Comment by Randolph Tan [ 08/Jun/15 ] |
|
FYI: Any command that uses Future does not support stale config retry correctly (it should be using Strategy::commandOp). |
| Comment by Adam Midvidy [ 08/Jun/15 ] |
|
Methods that MongoS uses to send commands to shards that bypass DBClientWithCommands::runCommand:
kaloian.manassiev and renctan, which of these abstractions are going to be removed as part of the mongos refactor, and which are going to need to support OP_COMMAND? cc acm schwerin |
| Comment by Githook User [ 05/Jun/15 ] |
|
Author: {u'username': u'amidvidy', u'name': u'Adam Midvidy', u'email': u'amidvidy@gmail.com'}Message: |
| Comment by Githook User [ 05/Jun/15 ] |
|
Author: {u'username': u'amidvidy', u'name': u'Adam Midvidy', u'email': u'amidvidy@gmail.com'}Message:
|