incubator-couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randall Leeds (JIRA)" <j...@apache.org>
Subject [jira] Updated: (COUCHDB-705) hard limit on number of concurrent requests
Date Wed, 07 Apr 2010 18:12:33 GMT

     [ https://issues.apache.org/jira/browse/COUCHDB-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Randall Leeds updated COUCHDB-705:
----------------------------------

    Attachment: mochiweb_max_connections.patch

New version of the patch.

Registered a listener with couch_config to restart the mochiweb server if max_connections
is changed via /_config
Added an appropriate default line to deafult.ini.tpl.in so that users see the option in their
config file.

I hope this can be included. It's simple and complete afaict.

> hard limit on number of concurrent requests
> -------------------------------------------
>
>                 Key: COUCHDB-705
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-705
>             Project: CouchDB
>          Issue Type: Improvement
>    Affects Versions: 0.11
>         Environment: all
>            Reporter: Randall Leeds
>            Priority: Minor
>         Attachments: mochiweb_max_connections.patch
>
>
> mochiweb has a default maximum number of concurrent requests set to 2048. For some deployments
this is too small. Many simultaneous replications can easily exhaust this limit and cause
slow responses to client requests.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message