[SERVER-48214] ReplSetTest awaitReplication is too verbose Created: 14/May/20 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | former-quick-wins | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Participants: |
| Description |
|
While awaitReplication is looping, it logs messages every 2 tenths of a second. In some cases, it can log 9 or more lines in each batch of messages. For some tests, especially when they are failing, this can overwhelm the log and cause lengthy load times and web browser memory issues, making the BF diagnosis experience worse than it needs to be. I think some of these messages can be eliminated or combined while still giving all the information. Example:
|
| Comments |
| Comment by Eric Milkie [ 10/Jul/20 ] |
|
I think that solution would slow down the test suite, so I'd rather avoid that. Can we eliminate extraneous messages instead? For example, this message is useless since the info is already gleanable in other messages: This message doesn't need to be on a separate line: This message has little utility and should be removed, since the following line makes it obvious what was being checked: |
| Comment by Judah Schvimer [ 10/Jul/20 ] |
|
milkie, would assert.soon having an exponential backoff be an acceptable solution? |