Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E59B010BF5 for ; Fri, 10 Jan 2014 12:43:10 +0000 (UTC) Received: (qmail 3725 invoked by uid 500); 10 Jan 2014 12:43:04 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 3668 invoked by uid 500); 10 Jan 2014 12:42:56 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 3655 invoked by uid 99); 10 Jan 2014 12:42:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Jan 2014 12:42:52 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [78.8.8.178] (HELO mail.getbacksa.pl) (78.8.8.178) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Jan 2014 12:42:46 +0000 Received: from SEX1.getback.ad2008r2.corp ([::1]) by SEX1.getback.ad2008r2.corp ([::1]) with mapi id 14.02.0342.003; Fri, 10 Jan 2014 13:42:25 +0100 From: Igor Klimer To: "user@couchdb.apache.org" Subject: ODP: Error during compaction Thread-Topic: Error during compaction Thread-Index: Ac8NRoszzH/UN0RdSuGabwDehlol+wAABaSAAAGufwAAI5dF1QAGI4WAAAJ0mok= Date: Fri, 10 Jan 2014 12:42:24 +0000 Message-ID: References: , , In-Reply-To: Accept-Language: pl-PL, en-US Content-Language: pl-PL X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.2.131] Content-Type: text/plain; charset="windows-1250" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Yes, I've already done that after the very fist attempt at compaction (the = one that failed because of lack of disk space). And it resulted in the seco= nd fail (on Windows), then the same on Linux - I always deleted the incompl= ete (about 50% of the database, around 50GB) .compact file before running t= he compaction again. So I was always doing compaction from scratch. Best regards, Igor Klimer ________________________________________ Od: Robert Samuel Newson [rnewson@apache.org] Wys=B3ano: 10 stycznia 2014 13:08 Do: user Temat: Re: Error during compaction Thanks! that=92s very useful. Hitting end of disk certainly feels like a ca= use here. Since the compaction has never completed, I suggest we redo compa= ction from scratch. 1) stop couchdb 2) delete (or move aside) the dbname.compact file for this database 3) start couchdb 4) compact the db Whether it works or not, please let us know. B. On 10 Jan 2014, at 08:25, Igor Klimer wrote: >> Given that you=92re at 100Gb and compacting for the first time, can you = tell us if you were running on older couchdb versions that 1.2.0 between db= creation and today? > > No, we've been running 1.2.0 from the start (around Oct 2012), then switc= hed to Ubuntu and 1.5.0. > >> Do you have free disk space? > Yes, there's about 150% of the DB's size worth of free space :) I forgot = to mention ("OK, here we go, the user will confess to some sin he committed= and is ashamed of and is most likely the reason for this failure") that we= 've run the compaction once before the error on Windows I mentioned below, = but it failed because of insufficient disk space - so I double checked befo= re running the compaction again if there's enough space. Here's the log, if= it's any helpful: http://pastebin.com/S1URXN0p > Do you think it could have left the database in some corrupted state? It = seems it failed at a different part then the two next attempts (and, as far= as I understand, compaction is just copying over the database while prunin= g the old revisions and deleted documents). > > Thank you for your time and help and best regards, > Igor Klimer > ________________________________________ > Od: Robert Samuel Newson [rnewson@apache.org] > Wys=B3ano: 9 stycznia 2014 17:13 > Do: user > Temat: Re: Error during compaction > > Do you have free disk space? > > On 9 Jan 2014, at 15:25, Robert Samuel Newson wrote: > >> >> Given that you=92re at 100Gb and compacting for the first time, can you = tell us if you were running on older couchdb versions that 1.2.0 between db= creation and today? >> >> B. >> >> On 9 Jan 2014, at 14:39, Igor Klimer wrote: >> >>> Hi all, >>> I've stumbled upon a peculiar problem while trying to compact (for the = first time) a large(-ish) database (~100GB at that time). At about 50% it f= ailed with this error: http://pastebin.com/qeaZNHMj >>> This is from Windows Server 2008 R2 Enterprise with Couchdb 1.2.0. >>> I figured that it might be a bug in the Windows build (Erlang on Window= s? C'mon, that can't be good ;)) or already fixed in a newer version. Some = time later we migrated the server to a Linux box running Ubuntu 12.04.3 LTS= (GNU/Linux 3.8.0-33-generic x86_64) and update Couchdb to 1.5.0. >>> Unfortunately, the same error occurred: http://pastebin.com/feJWu7bN >>> >>> I've tried wrapping my head around that error, googling it, checking th= is mail list but to no avail :) So if anyone can give me any pointers as to= what might be causing this problem, I'd be very grateful. >>> >>> Best regards, >>> Igor Klimer >>> >>> (sorry for the footer that will probably follow, unfortunately it's add= ed for all outgoing external mail...) >>> >>> >>> >>> ------------------------------- getBACK S.A., ul. Powsta=F1c=F3w =8Cl=B9skich 2-4, 53-333 Wroc=B3aw Sad rejestrowy: S=B9d Rejonowy dla Wroc=B3awia - Fabrycznej, VI Wydzia=B3 G= ospodarczy KRS. Numer KRS: 0000413997 NIP: 8992733884 REGON: 021829989 Wysoko=9C=E6 kapita=B3u zak=B3adowego op=B3aconego w ca=B3o=9Cci: 4 000 000= ,00 z=B3 Zamieszczenie powy=BFszych danych identyfikuj=B9cych getBACK S.A. stosownie= do art. 374 par.1 Kodeksu sp=F3=B3ek handlowych nie jest r=F3wnoznaczne z = handlowym charakterem dostarczonej do Pa=F1stwa wiadomo=9Cci e-mailowej i p= ozostaje bez wp=B3ywu na interpretacje zawartych w niej o=9Cwiadcze=F1. Niniejszy e-mail oraz wszelkie za=B3=B9czone do niego pliki s=B9 poufne i m= og=B9 podlega=E6 ochronie prawnej. Je=BFeli nie jest Pan/Pani zamierzonym a= dresatem powy=BFszej wiadomo=9Cci, nie mo=BFe jej Pan/Pani ujawnia=E6, kopi= owa=E6, dystrybuowa=E6, ani tez w =BFaden inny spos=F3b udost=EApnia=E6 lub= wykorzystywa=E6. O b=B3=EAdnym zaadresowaniu wiadomo=9Cci prosimy niezw=B3= ocznie poinformowa=E6 nadawc=EA i usun=B9=E6 wiadomo=9C=E6. This e-mail message may contain confidential and/or privileged information.= If you are not the intended recipient (or have received this e-mail in err= or) please notify the sender immediately and destroy this e-mail. Any unaut= horized copying, disclosure or distribution of the material in this e-mail = is strictly forbidden.