[SERVER-48085] Suppress "unrecognized parameter waitForStepDownOnNonCommandShutdown" log Created: 11/May/20 Updated: 29/Oct/23 Resolved: 14/May/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | A. Jesse Jiryu Davis | Assignee: | Tess Avitabile (Inactive) |
| 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 2020-05-18 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 40 | ||||||||||||||||
| Description |
|
In ReplSetTest, starting with
This can confuse humans and tools that search for assertion failures to diagnose test failures. I propose we check for this specific error from setParameter and suppress it in replsettest.js, while allowing other errors from setParameter to bubble up. |
| Comments |
| Comment by Githook User [ 14/May/20 ] |
|
Author: {'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com', 'username': 'tessavitabile'}Message: |
| Comment by Tess Avitabile (Inactive) [ 11/May/20 ] |
|
Got it, thanks for pointing that out. |
| Comment by Max Hirschhorn [ 11/May/20 ] |
|
tess.avitabile, I don't believe the changes from 20df781 as part of |
| Comment by Tess Avitabile (Inactive) [ 11/May/20 ] |
|
I agree! I addressed this in |
| Comment by Max Hirschhorn [ 11/May/20 ] |
|
Is there a reason we call assert.commandWorked() inside of a try/catch block anyway? It seems like we could printjson() the response explicitly if all we were interested in was logging any errors via doassert() being called. |