Project

General

Profile

Feature #3965

upstart: ulimit -n hardcoded; doesn't use 'max open files' config setting

Added by Dan Mick about 11 years ago. Updated almost 6 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
Development
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

3900 tweaked the setting of ulimit -n "max open files" on all daemons in the cluster, but,
at present, we only have a solution for clusters that start with /etc/init.d/ceph; something
needs to happen for ceph-deploy and others (and perhaps ulimit -c unlimited as well, since
init.d/ceph does that too).

I tend to want to suggest that the daemons should be doing this themselves; it seems cleaner.

History

#1 Updated by Dan Mick about 11 years ago

  • Project changed from Ceph to devops

#2 Updated by Dan Mick about 11 years ago

I guess there are settings in the upstart config files, but they aren't derived from ceph.conf.
I imagine there are ways to do that, and we probably should. Not exactly sure how Chef might be
configured to start the daemons.

I was thinking maybe the daemons should do the setrlimit() calls themselves, but Josh has
expressed the opinion that it's more conventional to do it outside the daemon.

#3 Updated by Sage Weil about 11 years ago

  • Subject changed from ulimit -n needs to happen for non-/etc/init.d/ceph startup to update: ulimit -n hardcoded; doesn't use 'max open files' config setting

#4 Updated by Sage Weil about 11 years ago

  • Subject changed from update: ulimit -n hardcoded; doesn't use 'max open files' config setting to upstart: ulimit -n hardcoded; doesn't use 'max open files' config setting

#5 Updated by Sage Weil about 11 years ago

  • Tracker changed from Bug to Feature

#6 Updated by Sage Weil almost 6 years ago

  • Status changed from New to Rejected

Also available in: Atom PDF