| Summary: | RFE: Allow ulimit -n (open files) value for vdsmd to be set in vdsm.conf | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Mark Huth <mhuth> | ||||||
| Component: | vdsm | Assignee: | Dan Kenigsberg <danken> | ||||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | yeylon <yeylon> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | unspecified | CC: | abaron, bazulay, danken, iheim, srevivo, yeylon, ykaul | ||||||
| Target Milestone: | --- | Keywords: | FutureFeature | ||||||
| Target Release: | 3.3.4 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Enhancement | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2011-12-26 19:50:56 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
Created attachment 509866 [details]
patch 2 of 2: document max_open_files in vdsm.conf.sample
Yeah, hard-coded constants are not nice. Let's consider it for 6.3 We should have `ulimit -u` configurable, too. oops, http://gerrit.usersys.redhat.com/948 already committed Mon Oct 3 10:39:28 2011 +0200 posted another patch for max processes http://gerrit.ovirt.org/638 |
Created attachment 509865 [details] patch 1 of 2: in /etc/rc.d/init.d/vdsmd, use get-config-item to fetch the max_open_files value from vdsm.conf Description of problem: We had a case recently where the customer was encountering errors in vdsm.log similar to: IOError: [Errno 24] Too many open files: '/proc/mounts' ... and vdsmd was dying. A value of 4096 is hardcoded into /etc/rc.d/init.d/vdsmd: [ `ulimit -n` -lt 4096 ] && ulimit -n 4096 It would be 'nicer' to be able to control this via the vdsm.conf file, in case it needs to be made higher than 4096. Attached files provide a mechanism to do this. Version-Release number of selected component (if applicable): Latest RHEVH