[ https://issues.apache.org/jira/browse/ACCUMULO-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922924#comment-13922924 ]
Mike Drob commented on ACCUMULO-2436: ------------------------------------- There's about 2000+ major compactions queued up. It looks like this isn't actually causing any errors for the system, just a bunch of noisy messages. > Errors during CI > ---------------- > > Key: ACCUMULO-2436 > URL: https://issues.apache.org/jira/browse/ACCUMULO-2436 > Project: Accumulo > Issue Type: Bug > Affects Versions: 1.4.4 > Environment: 1.4.5-SNAPSHOT, sha: 0f23245 > cdh 4.5.0 > Reporter: Mike Drob > Labels: 14_qa_bug > > In the "Table Problems" page of the monitor, errors started with: > {{java.io.IOException: java.io.FileNotFoundException: File > /accumulo/recovery/48bad96b-4e57-4989-80b8-4844268e931a.recovered does not > exist.}} > Then there are a bunch (50+) errors that look like: > {{java.io.IOException: Unable to find recovery files for extent > 1;68c059;68b05af logEntry: 1;68c059; 48bad96b-4e57-4989-80b8-4844268e931a > (1539)}} > but with different extents and log entries (same uuid, which makes sense). > Meanwhile, on the "Recent Logs" page there's a bunch of {{10.0.0.1:10011 > reports assignment failed for tablet 1;68c059;68b05af}}. The extents all > match up with the other page, pairwise. > About 25 minutes later, there is > {noformat} > Unable to cleanly close logger 10.0.0.1:11224: > org.apache.thrift.transport.TTransportException: java.io.IOException: Broken > pipe > Unable to connect to 10.0.0.1:11224: > org.apache.thrift.transport.TTransportException: java.net.ConnectException: > Connection refused > unable to get tablet server status 10.0.0.1:10011[143d763f42201b5] > java.net.ConnectException: Connection refused > {noformat} > After that I get the same error from ACCUMULO-2150. -- This message was sent by Atlassian JIRA (v6.2#6252)