[SERVER-6889] Refuse to start on NUMA hardware if "numactl --interleave=all" is not set, bypass with --overrideNUMAwarning Created: 29/Aug/12 Updated: 14/Mar/17 Resolved: 25/Jun/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Tad Marshall | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux |
||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
The mongod server is known to suffer from serious performance problems when running on Linux systems on Non-Uniform Memory Access hardware unless mongod is started by numactl with the --interleave=all option. Today's server logs a large warning when started in this condition. Users may or may not notice the warning that mongod logs at startup, but even if they notice the warning they may not associate it with performance problems that crop up later. These users may blame mongod for the poor performance and not realize that they have missed a key configuration step. These users would be better served by having mongod refuse to start up in cases where they are likely to see problems later on. In the cases where it really is desired to run on NUMA hardware without memory interleaving, a command line switch would make this possible. Proposal:
The goal is to increase product satisfaction by preventing a common case of misconfiguration. |