[SERVER-17522] THP startup warnings can become stale Created: 10/Mar/15 Updated: 23/Feb/23 Resolved: 24/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | 3.0.0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kevin Pulo | Assignee: | Backlog - Service Architecture |
| Resolution: | Won't Do | Votes: | 3 |
| Labels: | platforms-re-triaged, re-triaged-ticket | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||
| Assigned Teams: |
Service Arch
|
||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||||||||||||||||||
| Description |
|
Unlike most (all?) other things that startup warnings warn about, Transparent Hugepages (THP) can be disabled without requiring the mongod to be restarted. This means that a startup warning about /sys/kernel/mm/transparent_hugepage/enabled or /sys/kernel/mm/transparent_hugepage/defrag can become stale, and no longer indicative of an actual problem. It would be useful if this could somehow be handled. |
| Comments |
| Comment by Lauren Lewis (Inactive) [ 24/Feb/22 ] |
|
We haven’t heard back from you for at least one calendar year, so this issue is being closed. If this is still an issue for you, please provide additional information and we will reopen the ticket. |
| Comment by Daniel Pasette (Inactive) [ 11/Mar/15 ] |
|
I don't think reward is worth the work to dynamically update the warning. This will be a rare case. If it turns out to become a problem, we can re-evaluate. |