[SERVER-35846] sanitize replication thread names Created: 27/Jun/18 Updated: 29/Oct/23 Resolved: 07/Nov/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Pavithra Vetriselvan |
| Resolution: | Fixed | Votes: | 2 |
| Labels: | former-quick-wins | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Repl 2019-10-21, Repl 2019-11-04, Repl 2019-11-18 |
| Participants: |
| Description |
|
The naming for replication helper threads is starting to get out of hand. We currently have the following names for threads: These names are not very descriptive, other than the "writer worker" names. While they don't necessarily need to explain exactly what is going on, it would be helpful if the names were chosen to be less generic and more easily searched-for in the code. |
| Comments |
| Comment by Githook User [ 07/Nov/19 ] |
|
Author: {'username': 'pvselvan', 'email': 'pavithra.vetriselvan@mongodb.com', 'name': 'Pavithra Vetriselvan'}Message: |
| Comment by Judah Schvimer [ 24/Jul/19 ] |
|
milkie has reiterated that this continues to bite him in diagnosing failures. I can admit that due to this I never look at replication thread names. |
| Comment by Tess Avitabile (Inactive) [ 03/Jul/18 ] |
|
Nominating this for the quick wins bucket, since it would aid build failure diagnosis. |