Details
-
Bug
-
Status: Closed
-
Blocker
-
Resolution: Fixed
-
1.1.1, 1.3
-
None
Description
Via Stefan Kögl on dev@:
Another thing I noticed during my tests of CouchDB 1.2.x. I redirected
live traffic to the instance and after a rather short time, requests
were failing with the following information in the logs:
[Sun, 18 Mar 2012 16:39:24 GMT] [error] [<0.27554.2>]
{error_report,<0.31.0>,
{<0.27554.2>,std_error,
[
,
"Accept failed error",
"
"]}}
[Sun, 18 Mar 2012 16:39:24 GMT] [error] [<0.27554.2>]
{error_report,<0.31.0>,
{<0.27554.2>,crash_report,
[[{initial_call,
{mochiweb_acceptor,init,
['Argument_1','Argument_2',
'Argument__3']}},
,
,
{error_info,
{exit,
,
[
,
]}},
,
,
,
,
,
,
,
,
],
[]]}}
I think "emfile" means that CouchDB (or mochiweb?) couldn't open any
more files / connections. I've set the (hard and soft) nofile limit for
user couchdb to 4096, but didn't raise the ERL_MAX_PORTS accordingly.
Anyway, as soon as the error occured, CouchDB started writing most of my
view files from scratch, rendering the instance unusable.
I'd expect CouchDB to fail more gracefully when the maximum number of
open files is reached. Is this a bug or expected behaviour?