couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From A Hakeem <alhak...@ipextelecom.net>
Subject Re: [jira] Closed: (COUCHDB-590) Support resource limit configuration in the init scripts
Date Wed, 16 Jun 2010 22:32:12 GMT
unsubscribe

On Wed, Jun 16, 2010 at 11:30 PM, Randall Leeds (JIRA) <jira@apache.org>wrote:

>
>     [
> https://issues.apache.org/jira/browse/COUCHDB-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Randall Leeds closed COUCHDB-590.
> ---------------------------------
>
>    Resolution: Invalid
>
> Closing as invalid.
>
> This is distribution specific. For example, on most Linux systems with pam
> installed the appropriate place to do this would be
> /etc/security/limits.conf.
>
> > Support resource limit configuration in the init scripts
> > --------------------------------------------------------
> >
> >                 Key: COUCHDB-590
> >                 URL: https://issues.apache.org/jira/browse/COUCHDB-590
> >             Project: CouchDB
> >          Issue Type: Improvement
> >          Components: Infrastructure
> >            Reporter: Randall Leeds
> >            Assignee: Noah Slater
> >            Priority: Minor
> >         Attachments: ulimit.patch
> >
> >   Original Estimate: 0h
> >  Remaining Estimate: 0h
> >
> > It would be nice to specify some resource limits when spawning couchdb
> from the init scripts.
> > I've seen high load result in mochiweb accept errors, for example, and
> increasing the file descriptor limit solved the problem.
> > I'm attaching a patch that allows any options to be passed to ulimit via
> /etc/defaults/couchdb
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message