transient errors with couch DB (re-post)

[Valentin Kuznetsov]

Hi,



I'm developing application based on couch db and time to time
experience different error messages and crashes with couch, version
0.9.0. We have a large documents, e.g. 64K, which split into 1K chunks
(rows) for bulk injection. Each time I inject new chunk I also invoke
1 GET request to fetch 1 row in order to force view to index data.

So here are error messages:

[error] [<0.12304.2>] Uncaught error in HTTP request: {exit,normal}

[error] [<0.30955.5>] {error_report,<0.23.0>,
     {<0.30955.5>,crash_report,
      [[{initial_call,{mochiweb_socket_server,acceptor_loop,
['Argument__1']}},
        {pid,<0.30955.5>},
        {registered_name,[]},
        {error_info,
            {error,
                {case_clause,{error,einval}},
                [{mochiweb_request,get,2},
                 {couch_httpd,handle_request,4},
                 {mochiweb_http,headers,5},
                 {proc_lib,init_p_do_apply,3}]}},
        {ancestors,

[couch_httpd,couch_secondary_services,couch_server_sup,<0.1.0>]},
        {messages,[]},
        {links,[<0.53.0>,#Port<0.1735>]},
        {dictionary,[{mochiweb_request_qs,[{"limit","1"}]}]},
        {trap_exit,false},
        {status,running},
        {heap_size,6765},
        {stack_size,24},
        {reductions,3888}],
       []]}}
[error] [<0.53.0>] {error_report,<0.23.0>,
     {<0.53.0>,std_error,
      {mochiweb_socket_server,235,{child_error,{case_clause,
{error,einval}}}}}}

=ERROR REPORT==== 2-Jul-2009::10:21:33 ===
{mochiweb_socket_server,235,{child_error,{case_clause,{error,einval}}}}

So, I made a stand-alone program and to my surprise the errors are
transient. I re-run my stand-alone program with the same doc several
times and I can either inject all data just fine or get errors shown
above in no particular order (I mean I can see 1 or more errors and
none or either of those).

Originally I posted tar ball to this thread w/ my program, but it error


Thank you,
Valentin

my original mail was not parsed correctly by mailing list, so I re- post it. occurred on mailing list (may be it's not allowed to send attachements), so I decided to re-post my question without it. But if someone interesting I can send it over.

smime.p7s
Description: S/MIME cryptographic signature