[SERVER-41453] Raise the minimum file handle limit to trigger a startup warning Created: 03/Jun/19 Updated: 29/Oct/23 Resolved: 01/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Nic Cottrell | Assignee: | Mathew Robinson (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Dev Tools 2019-08-12 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||
| Description |
|
Currently, a startup warning is only triggered if the nofile limit is less than 1000. However, the production notes recommend a value of 64000. Shouldn't the warning be triggered for a higher threshold, say 32000 to catch poorly optimized systems? There's probably many even at 1024 which get no warning. |
| Comments |
| Comment by Githook User [ 01/Aug/19 ] |
|
Author: {'name': 'Mathew Robinson', 'email': 'chasinglogic@gmail.com', 'username': 'chasinglogic'}Message: |