CouchDB terminates unexpectedly

Question

Today I wrote a performance testing program to insert data and add attachments to couchdb. The server software is couchbase (which is the couchdb shell), and the operating system is a Windows 2003 server. The program is developed in C #, and the couchdb driver is LoveSeat (which encapsulates some http methods for working with couchdb). The data is quite simple, but the attachments are not small, about 70 kb each. There were about 200 attachments, and I attached them many times. I started 5 threads in the client program.

Everything looked good until the couchdb server terminated unexpectedly. In fact, this was not the first time that he crashed. At first I thought it was because of the client program. But finally, I found that couchdb crashed. I don’t think it was due to data or attachment. because I inserted the same data and re-added the same attachment. The program runs for about an hour without problems, until it crashes.

[Tue, 05 Jul 2011 11:00:19 GMT] [info] [<0.142.0>] 192.168.1.135 - - 'GET' /test/67366 200 [Tue, 05 Jul 2011 11:00:19 GMT] [info] [<0.108.0>] 192.168.1.135 - - 'GET' /test/7136 200 [Tue, 05 Jul 2011 11:00:19 GMT] [info] [<0.108.0>] 192.168.1.135 - - 'GET' /test/47306 200 [Tue, 05 Jul 2011 11:00:19 GMT] [info] [<0.108.0>] 192.168.1.135 - - 'GET' /test/27257 200 [Tue, 05 Jul 2011 11:00:19 GMT] [info] [<0.108.0>] 192.168.1.135 - - 'PUT' /test/7136/f?rev=1-334efd144dcdc52fd3a3a981dce4472f 201 [Tue, 05 Jul 2011 11:00:25 GMT] [error] [<0.145.0>] ** Generic server <0.145.0> terminating ** Last message in was {pread_iolist,4294342003} ** When Server state == {file,{file_descriptor,prim_file,{#Port<0.3143>,1464}}, 0,4295164786} ** Reason for termination == ** {{badmatch,{ok,<<183,92,29,219,169,127,153,2,50,217,252,186,178,175,202, 144,215,209,191,69,109,230,227,154,114,174,173,157,231, 153,246,124,105,239,174,51,143,24,108,175,101,215,175, 221,35,99,53,124,108,109,249,112,202,29,85,87,81,176,94, 219,11,103,129,231,25,111,242,108,246,207,107,72,173,172, 57,246,195,16,236,79,243,134,211,93,131,218,180,93,240, 173,213,199,226,175,176,217,250,154,89,39,237,157,250,77, 173,151,156,139,248,106,85,21,134,253,85,234,108,85,208, 67,177,130,124,247,161,98,77,173,126,170,111,80,84,45, 212,201,72,149,90,138,252,89,23,85,165,252,105,187,191, 41,86,125,148,106,149,175,252,78,185,198,154,207,172,142, 148,101,83,140,99,222,102,26,41,131,206,132,221,31,74,3, 172,176,158,236,136,71,120,169,63,35,161,251,208,86,202, 1,95,208,25,51,76,250,100,182,177,122,31,91,230,249,214, 245,229,250,212,118,86,167,120,116,6,173,78,113,18,171, 143,215,191,38,207,51,92,150,10,10,83,164,98,154,181,157, ......... a loooooot of numbers. 

Answer 1

Last completion:

couchbase 1.02 does NOT support data files larger than 4 GB on a Windows 2003 32-bit machine.

couchbase 2.0 Developer prereview version DOES supports a data file larger than 4 GB on a 32-bit Windows 2003 machine. But, as far as I can tell, version 2.0 is at least 5 times slower than version 1.02.

couchdb 1.1 from this link DOES supports a file larger than 4 GB on a 32-bit Windows 2003 machine. But it's as slow as couchbase 2.0.

Couchdb tooooo slow for Windows (at least in my case it is slow). Finally, I tried using mysql to store files. Mysql is 8 times faster! inserting an attachment into couchdb takes 650 ms, and the number for mysql is only 80 ms.

Answer 2

I'm sorry you had this error. May I suggest posting this question on the Couchbase forums? Our support team tracks those closer than SO: http://www.couchbase.org/forums/

Answer 3

I think I found a reason. File size reached 4 GB. But according to this wiki page , the Erlang / OTP R14B01 release no longer has this error. Therefore, I think couchbase uses the embedded erlang / otp version that precedes R14B01. (I also installed standalone Erlang / OTP R14B03 on the machine, but it doesn't seem to be used)