[SERVER-44508] Add maxAwaitTimeMS and topologyVersion to isMaster command Created: 08/Nov/19 Updated: 29/Oct/23 Resolved: 22/Nov/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.3 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | A. Jesse Jiryu Davis | Assignee: | Haley Connelly |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Repl 2019-11-18, Repl 2019-12-02 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Also return a dummy topologyVersion field in the isMaster reply. |
| Comments |
| Comment by Githook User [ 22/Nov/19 ] |
|
Author: {'name': 'Haley Connelly', 'username': 'haleyConnelly', 'email': 'haley.connelly@10gen.com'}Message: |
| Comment by Tess Avitabile (Inactive) [ 14/Nov/19 ] |
|
As part of this ticket, I think we can also parse maxAwaitTimeMS and topologyVersion and validate their types. This will allow us to use the fields in |
| Comment by Haley Connelly [ 14/Nov/19 ] |
|
Currently, our isMaster command can take in arbitrary parameters without failing in our integration tests. eg) db.runCommand( {isMaster: 1, maxAwaitTimeMS: 1}) does fail or appear to yield any telling errors. For this reason, I believe that the scope of this ticket is now limited to introducing the dummy TopologyVersion field to the isMaster reply. |