couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Clement Law (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-536) CouchDB HTTP server stops accepting connections
Date Tue, 16 Dec 2014 11:41:13 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248168#comment-14248168
] 

Clement Law commented on COUCHDB-536:
-------------------------------------

Yes, what I have decided to do for now is to increase the maximum of open files to something
larger (2048 etc). The most desirable thing to have is for the client making the request to
be able to tell the server how long it will wait around for before giving up. That way, the
server can know how long to run a process for before giving up. Currently, the server doesn't
know whether a client is still waiting for a reply until it tries using the socket.

> CouchDB HTTP server stops accepting connections
> -----------------------------------------------
>
>                 Key: COUCHDB-536
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-536
>             Project: CouchDB
>          Issue Type: Bug
>          Components: HTTP Interface
>    Affects Versions: 0.10, 1.1
>         Environment: Ubuntu Linux 8.04 32bit and 64bit with Erlang R13B01
> or Ubuntu Linux 8.04 64bit with Erlang R14B02
>            Reporter: Simon Eisenmann
>         Attachments: couchdb_database_open-week.png, couchdb_httpd_request_methods-week.png,
couchdb_httpd_response_codes-week.png
>
>
> Having 3 Couches all replicating a couple of databases to each other (pull replication
with a update notification process) the HTTP service on any of the Couches stops working at
some point (when running for a couple of ours with constant changes on all databases and servers).
> This is the error when a new HTTP request comes in:
> =ERROR REPORT==== 19-Oct-2009::10:18:55 ===
>     application: mochiweb
>     "Accept failed error"
>     "{error,enfile}"
> [error] [<0.21619.12>] {error_report,<0.24.0>,
>     {<0.21619.12>,crash_report,
>      [[{initial_call,{mochiweb_socket_server,acceptor_loop,['Argument__1']}},
>        {pid,<0.21619.12>},
>        {registered_name,[]},
>        {error_info,
>            {exit,
>                {error,accept_failed},
>                [{mochiweb_socket_server,acceptor_loop,1},
>                 {proc_lib,init_p_do_apply,3}]}},
>        {ancestors,
>            [couch_httpd,couch_secondary_services,couch_server_sup,<0.1.0>]},
>        {messages,[]},
>        {links,[<0.66.0>]},
>        {dictionary,[]},
>        {trap_exit,false},
>        {status,running},
>        {heap_size,233},
>        {stack_size,24},
>        {reductions,202}],
>       []]}}
> [error] [<0.66.0>] {error_report,<0.24.0>,
>     {<0.66.0>,std_error,
>      {mochiweb_socket_server,225,{acceptor_error,{error,accept_failed}}}}}
> To me this seems like it runs out of threads or sockets to handle the new connection
or somewhat like this.
> Also i see in this setup that if i put lots of changes in a short time at some point
the replication process hangs (never finishes) and when trying to restart the same replication
once again is not possible and resulting in a timeout.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message