John Nagro created BOOKKEEPER-230: ------------------------------------- Summary: GarbageCollectorThread Log Errors Key: BOOKKEEPER-230 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-230 Project: Bookkeeper Issue Type: Bug Components: bookkeeper-server Affects Versions: 4.1.0 Environment: architecture => i386 augeasversion => 0.9.0 ec2_instance_type => c1.medium ec2_kernel_id => aki-407d9529 ec2_profile => default-paravirtual hardwareisa => i686 hardwaremodel => i686 is_virtual => true kernel => Linux kernelmajversion => 2.6 kernelrelease => 2.6.18-274.7.1.el5xen kernelversion => 2.6.18 lsbdistcodename => Final lsbdistdescription => CentOS release 5.7 (Final) lsbdistid => CentOS lsbdistrelease => 5.7 lsbmajdistrelease => 5 lsbrelease => :core-4.0-ia32:core-4.0-noarch:graphics-4.0-ia32:graphics-4.0-noarch:printing-4.0-ia32:printing-4.0-noarch memoryfree => 1.08 GB memorysize => 1.70 GB memorytotal => 1.70 GB operatingsystem => CentOS operatingsystemrelease => 5.7 osfamily => RedHat path => /usr/share/maven2/apache-maven-2.0.9/bin:/usr/java/jdk1.6.0_23/bin:/sbin:/usr/sbin:/usr/share/maven2/apache-maven-2.0.9/bin:/usr/java/jdk1.6.0_23/bin:/sbin:/usr/sbin:/usr/local/bin:/bin:/usr/bin:/home/jnagro/bin physicalprocessorcount => 0 processor0 => Intel(R) Xeon(R) CPU E5410 @ 2.33GHz processor1 => Intel(R) Xeon(R) CPU E5410 @ 2.33GHz processorcount => 2 ps => ps -ef puppetversion => 2.6.14 rubysitedir => /usr/lib/ruby/site_ruby/1.8 rubyversion => 1.8.5 selinux => false swapfree => 895.96 MB swapsize => 895.99 MB timezone => EDT uniqueid => f20a156a uptime => 63 days uptime_days => 63 uptime_hours => 1534 uptime_seconds => 5523311 virtual => xenu Reporter: John Nagro Attachments: bookkeeper.log
I have been running a 4.1-SNAPSHOT build, which last commit was: commit f694716e289c448ab89cab5fa81ea0946f9d9193 Author: Flavio Paiva Junqueira <f...@apache.org> Date: Tue Apr 3 16:02:44 2012 +0000 BOOKKEEPER-207: BenchBookie doesn't run correctly (ivank via fpj) And I noticed lots of these lines in the logs: 2012-04-25 11:20:48,422 - ERROR [GarbageCollectorThread:EntryLogger@188] - Trying to delete an entryLog file that could not be found: 0.log 2012-04-25 11:20:48,422 - INFO [GarbageCollectorThread:GarbageCollectorThread@266] - Deleting entryLogId 1 as it has no active ledgers! 2012-04-25 11:20:48,422 - ERROR [GarbageCollectorThread:EntryLogger@188] - Trying to delete an entryLog file that could not be found: 1.log I made a new 4.1-SNAPSHOT build yesterday (4/25/2012) and installed it on one of the servers and restart it. Errors remain. I will attach logs. I haven't touched the servers since setup - ie no manual deletion of logs, etc. I do delete legers programmatically using the bookkeeper client (which i believe we're still at 4.0). I have also noticed BkRecoveryExceptions when trying to read ledgers off this cluster: org.apache.bookkeeper.client.BKException$BKLedgerRecoveryException at org.apache.bookkeeper.client.BKException.create(BKException.java:66) at org.apache.bookkeeper.client.LedgerHandle.readLastConfirmed(LedgerHandle.java:576) This exception isn't thrown all the time, but is a very frequent error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira