[SERVER-29771] Remove the 'forceerror' commmand Created: 21/Jun/17 Updated: 30/Oct/23 Resolved: 31/Jan/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.2 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Janna Golden |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding 2018-02-12 | ||||||||
| Participants: | |||||||||
| Description |
|
This command is only referenced in two JS tests and is not even documented, so we should get rid of it altogether. |
| Comments |
| Comment by Githook User [ 31/Jan/18 ] |
|
Author: {'email': 'golden.janna@gmail.com', 'name': 'jannaerin', 'username': 'jannaerin'}Message: |
| Comment by Andy Schwerin [ 17/Jul/17 ] |
|
Yeah, that sounds reasonable. Sharding can traige removing the forceerror from features2.js, I suppose. |
| Comment by Ian Whalen (Inactive) [ 17/Jul/17 ] |
|
schwerin sounds like this should be repurposed to remove the forceerror part of features2.js and go to Needs Triage and someone's backlog? |
| Comment by Andy Schwerin [ 27/Jun/17 ] |
|
I checked with the drivers authors, and I don't think we need the forceerror behavior anymore. It only appears in the server code base to test its own functionality, AFAICT. |