You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by Markus Jelsma <ma...@buyways.nl> on 2010/01/22 16:03:41 UTC

Strange error during indexing

Hello all,


I have a sharded setup using 4 couch nodes and 2 lounge nodes. Each couch has 
8 database shards and yesterday i imported some 150.000 user profiles for 
which i just made a simple view for testing.

Anyway, one instance of the 5th shard on the 4th node has had a problem during 
indexing and sends the following error to the couch log:

[Fri, 22 Jan 2010 13:29:11 GMT] [error] [<0.28173.12>] {error_report,<0.23.0>,
    {<0.28173.12>,crash_report,
     [[{initial_call,{mochiweb_socket_server,acceptor_loop,['Argument__1']}},
       {pid,<0.28173.12>},
       {registered_name,[]},
       {error_info,
           {error,
               {case_clause,{error,enotconn}},
               [{mochiweb_request,get,2},
                {couch_httpd,handle_request,5},
                {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,[#Port<0.160398>,<0.63.0>,#Port<0.160397>]},
       {dictionary,
           [{mochiweb_request_qs,[{"key","\"hotmail.com\""},
{"group","true"}]},
            {jsonp,undefined},
            {couch_drv_port,#Port<0.160398>}]},
       {trap_exit,false},
       {status,running},
       {heap_size,2584},
       {stack_size,24},
       {reductions,60611}],
      []]}}

[Fri, 22 Jan 2010 13:29:11 GMT] [error] [<0.63.0>] {error_report,<0.23.0>,
    {<0.63.0>,std_error,
     {mochiweb_socket_server,235,
         {child_error,{case_clause,{error,enotconn}}}}}}

[Fri, 22 Jan 2010 13:29:15 GMT] [info] [<0.28921.12>] checkpointing view 
update
at seq 11706 for idm5 _design/profiles



The problem persists when i remove the view index from disk and stop and start 
CouchDB. However, after i replicated the shard from some other node it was 
gone!

Can anyone tell me what this error actually means and how we can avoid it in 
the future?



Cheers,

Re: Strange error during indexing

Posted by Chris Anderson <jc...@apache.org>.
On Fri, Jan 22, 2010 at 7:03 AM, Markus Jelsma <ma...@buyways.nl> wrote:
> Hello all,
>
>
> I have a sharded setup using 4 couch nodes and 2 lounge nodes. Each couch has
> 8 database shards and yesterday i imported some 150.000 user profiles for
> which i just made a simple view for testing.
>
> Anyway, one instance of the 5th shard on the 4th node has had a problem during
> indexing and sends the following error to the couch log:
>
> [Fri, 22 Jan 2010 13:29:11 GMT] [error] [<0.28173.12>] {error_report,<0.23.0>,
>    {<0.28173.12>,crash_report,
>     [[{initial_call,{mochiweb_socket_server,acceptor_loop,['Argument__1']}},
>       {pid,<0.28173.12>},
>       {registered_name,[]},
>       {error_info,
>           {error,
>               {case_clause,{error,enotconn}},
>               [{mochiweb_request,get,2},
>                {couch_httpd,handle_request,5},
>                {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,[#Port<0.160398>,<0.63.0>,#Port<0.160397>]},
>       {dictionary,
>           [{mochiweb_request_qs,[{"key","\"hotmail.com\""},
> {"group","true"}]},
>            {jsonp,undefined},
>            {couch_drv_port,#Port<0.160398>}]},
>       {trap_exit,false},
>       {status,running},
>       {heap_size,2584},
>       {stack_size,24},
>       {reductions,60611}],
>      []]}}
>
> [Fri, 22 Jan 2010 13:29:11 GMT] [error] [<0.63.0>] {error_report,<0.23.0>,
>    {<0.63.0>,std_error,
>     {mochiweb_socket_server,235,
>         {child_error,{case_clause,{error,enotconn}}}}}}
>
> [Fri, 22 Jan 2010 13:29:15 GMT] [info] [<0.28921.12>] checkpointing view
> update
> at seq 11706 for idm5 _design/profiles
>
>
>
> The problem persists when i remove the view index from disk and stop and start
> CouchDB. However, after i replicated the shard from some other node it was
> gone!
>
> Can anyone tell me what this error actually means and how we can avoid it in
> the future?
>

This looks unrelated to view index generation. It looks like CouchDB
was having trouble opening sockets.

That doesn't explain why rebuilding the node with identical data fixed things...

Chris

>
>
> Cheers,
>



-- 
Chris Anderson
http://jchrisa.net
http://couch.io