Server crashes after successfull compaction
-------------------------------------------
Key: COUCHDB-970
URL: https://issues.apache.org/jira/browse/COUCHDB-970
Project: CouchDB
Issue Type: Bug
Components: Database Core
Affects Versions: 0.11.2
Environment: Linux 2.6.18-194.11.3.el5 #1 SMP Mon Aug 30 16:19:16 EDT
2010 x86_64 x86_64 x86_64 GNU/Linux
Reporter: Rudi Benkovic
Our photos DB contains about 15K documents with 5-6 attachments per document
which results in a ~41GB database. Compacting this database (by removing the
original 30K documents to 15K) took a while, but after the temp file is
successfully switched, it crashes the whole server with these errors:
----------------------
[Mon, 29 Nov 2010 15:24:52 GMT] [error] [<0.186.0>] ** Generic server <0.186.0>
terminating
** Last message in was {'$gen_cast',
{compact_done,
"/home/couchdb/photos.couch.compact"}}
** When Server state == {db,<0.185.0>,<0.186.0>,<0.4488.3>,
<<"1291039821602632">>,<0.183.0>,<0.209.0>,
{db_header,5,320843,0,
{81045895963,{12262,39070}},
{81045898520,51332},
nil,0,nil,nil,1000},
320843,
{btree,<0.183.0>,
{81045895963,{12262,39070}},
#Fun<couch_db_updater.7.82129660>,
#Fun<couch_db_updater.8.42953822>,
#Fun<couch_btree.5.124754102>,
#Fun<couch_db_updater.9.115326703>},
{btree,<0.183.0>,
{81045898520,51332},
#Fun<couch_db_updater.10.103072508>,
#Fun<couch_db_updater.11.104248294>,
#Fun<couch_btree.5.124754102>,
#Fun<couch_db_updater.12.125559248>},
{btree,<0.183.0>,nil,
#Fun<couch_btree.0.83553141>,
#Fun<couch_btree.1.30790806>,
#Fun<couch_btree.2.124754102>,nil},
320843,<<"photos">>,"/home/couchdb/photos.couch",
[],[],nil,
{user_ctx,null,[],undefined},
nil,1000,
[before_header,after_header,on_file_open]}
** Reason for termination ==
** {timeout,
{gen_server,call,
[<0.185.0>,
{db_updated,
{db,<0.185.0>,<0.186.0>,nil,<<"1291039821602632">>,<0.4617.3>,
<0.4619.3>,
{db_header,5,320843,0,
{44797036682,{12262,39070}},
{44797027887,51332},
nil,0,nil,nil,1000},
320843,
{btree,<0.4617.3>,
{44797036682,{12262,39070}},
#Fun<couch_db_updater.7.82129660>,
#Fun<couch_db_updater.8.42953822>,
#Fun<couch_btree.5.124754102>,
#Fun<couch_db_updater.9.115326703>},
{btree,<0.4617.3>,
{44797027887,51332},
#Fun<couch_db_updater.10.103072508>,
#Fun<couch_db_updater.11.104248294>,
#Fun<couch_btree.5.124754102>,
#Fun<couch_db_updater.12.125559248>},
{btree,<0.4617.3>,nil,#Fun<couch_btree.0.83553141>,
#Fun<couch_btree.1.30790806>,
#Fun<couch_btree.2.124754102>,nil},
320843,<<"photos">>,"/home/couchdb/photos.couch",[],[],
nil,
{user_ctx,null,[],undefined},
nil,1000,
[before_header,after_header,on_file_open]}}]}}
[Mon, 29 Nov 2010 15:24:52 GMT] [error] [<0.186.0>] {error_report,<0.29.0>,
{<0.186.0>,crash_report,
[[{pid,<0.186.0>},
{registered_name,[]},
{error_info,
{exit,
{timeout,
{gen_server,call,
[<0.185.0>,
{db_updated,
{db,<0.185.0>,<0.186.0>,nil,
<<"1291039821602632">>,<0.4617.3>,<0.4619.3>,
{db_header,5,320843,0,
{44797036682,{12262,39070}},
{44797027887,51332},
nil,0,nil,nil,1000},
320843,
{btree,<0.4617.3>,
{44797036682,{12262,39070}},
#Fun<couch_db_updater.7.82129660>,
#Fun<couch_db_updater.8.42953822>,
#Fun<couch_btree.5.124754102>,
#Fun<couch_db_updater.9.115326703>},
{btree,<0.4617.3>,
{44797027887,51332},
#Fun<couch_db_updater.10.103072508>,
#Fun<couch_db_updater.11.104248294>,
#Fun<couch_btree.5.124754102>,
#Fun<couch_db_updater.12.125559248>},
{btree,<0.4617.3>,nil,
#Fun<couch_btree.0.83553141>,
#Fun<couch_btree.1.30790806>,
#Fun<couch_btree.2.124754102>,nil},
320843,<<"photos">>,
"/home/couchdb/photos.couch",[],[],nil,
{user_ctx,null,[],undefined},
nil,1000,
[before_header,after_header,on_file_open]}}]}},
[{gen_server,terminate,6},{proc_lib,init_p_do_apply,3}]}},
{initial_call,{couch_db_updater,init,['Argument__1']}},
{ancestors,[<0.185.0>,<0.182.0>]},
{messages,[{'EXIT',<0.4488.3>,normal},{'EXIT',<0.185.0>,shutdown}]},
{links,[]},
{dictionary,[]},
{trap_exit,true},
{status,running},
{heap_size,1346269},
{stack_size,23},
{reductions,16374254}],
[]]}}
----------------------
Is this fixed in 1.0.1 or is this a new issue?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
