[ https://issues.apache.org/jira/browse/COUCHDB-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790853#action_12790853 ]
Adam Kocoloski commented on COUCHDB-597: ---------------------------------------- The origin of this {#Ref<0.0.1832.61391>,3} message is a total mystery to me, but I know slyphon on IRC also saw this. We could guard against it by adding a catchall clause to couch_task_status:handle_info > Replication tasks crash. > ------------------------ > > Key: COUCHDB-597 > URL: https://issues.apache.org/jira/browse/COUCHDB-597 > Project: CouchDB > Issue Type: Bug > Components: Database Core > Affects Versions: 0.11 > Reporter: Robert Newson > > If I kick off 10 replication tasks in quick succession, occasionally one or > two of the replication tasks will die and not be resumed. It seems that the > stat tracking is a little buggy, and under stress can eventually cause a > permanent failure of the supervised replication task; > [Fri, 11 Dec 2009 19:00:08 GMT] [error] [<0.80.0>] {error_report,<0.30.0>, > {<0.80.0>,supervisor_report, > [{supervisor,{local,couch_rep_sup}}, > {errorContext,shutdown_error}, > {reason,killed}, > {offender, > [{pid,<0.6700.11>}, > {name,"fcbb13200a1618cf983b347f4d2c9835+create_target"}, > {mfa, > {gen_server,start_link, > [couch_rep, > ["fcbb13200a1618cf983b347f4d2c9835", > {[{<<"create_target">>,true}, > {<<"source">>,<<"http://node:5984/perf-p2">>}, > {<<"target">>,<<"perf-p2">>}]}, > {user_ctx,null,[<<"_admin">>]}], > []]}}, > {restart_type,temporary}, > {shutdown,1}, > {child_type,worker}]}]}} > [Fri, 11 Dec 2009 19:00:08 GMT] [error] [emulator] Error in process > <0.6705.11> with exit value: > {badarg,[{ets,insert,[stats_hit_table,{{couchdb,open_os_files},-1}]},{couch_stats_collector,decrement,1}]} -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.