Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Fri, 7 Feb 2014 16:04:21 +0000 (UTC)
From: "Luke Brassard (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12693747.1391723851171.5235.1391789061313@arcas>
In-Reply-To: <JIRA.12693747.1391723851171@arcas>
References: <JIRA.12693747.1391723851171@arcas>
Subject: [jira] [Commented] (ACCUMULO-2333) "File does not exist" error
 during client ingest with agitation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/ACCUMULO-2333?page=3Dcom.atlass=
ian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1=
3894664#comment-13894664 ]=20

Luke Brassard commented on ACCUMULO-2333:
-----------------------------------------

I think I still have the logs. I will try to pull all or the mentions of th=
e missing file shortly.

> "File does not exist" error during client ingest with agitation
> ---------------------------------------------------------------
>
>                 Key: ACCUMULO-2333
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2333
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.5.0
>            Reporter: Luke Brassard
>
> While running the agitator during a client ingest test, encountered a "Fi=
le does not exist" error that stuck in the Table Problems section of the mo=
nitor page.=20
> Confirmed that the file in question had been compacted away previously.
> While it appears that no data was lost, it is strange that the error surf=
aced and then seemed to right itself shortly thereafter. (though not updati=
ng the Table Problems section)
> Here is the stacktrace from the Monitor:
> {code}
> File does not exist: /accumulo/tables/2/t-00000dj/F0000dwj.rf at org.apac=
he.hadoop.hdfs.server.namenode.INodeFile.valueOf(INodeFile.java:61) at org.=
apache.hadoop.hdfs.server.namenode.INodeFile.valueOf(INodeFile.java:51) at =
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getBlockLocationsUpdate=
Times(FSNamesystem.java:1540) at org.apache.hadoop.hdfs.server.namenode.FSN=
amesystem.getBlockLocationsInt(FSNamesystem.java:1483) at org.apache.hadoop=
.hdfs.server.namenode.FSNamesystem.getBlockLocations(FSNamesystem.java:1463=
) at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getBlockLocations(=
FSNamesystem.java:1437) at org.apache.hadoop.hdfs.server.namenode.NameNodeR=
pcServer.getBlockLocations(NameNodeRpcServer.java:468) at org.apache.hadoop=
.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.getBlockLocat=
ions(ClientNamenodeProtocolServerSideTranslatorPB.java:269) at org.apache.h=
adoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtoc=
ol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java:59566) at org.apa=
che.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpc=
Engine.java:585) at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:928) at =
org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2053) at org.apache.=
hadoop.ipc.Server$Handler$1.run(Server.java:2049) at java.security.AccessCo=
ntroller.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Su=
bject.java:415) at org.apache.hadoop.security.UserGroupInformation.doAs(Use=
rGroupInformation.java:1491) at org.apache.hadoop.ipc.Server$Handler.run(Se=
rver.java:2047)
> {code}


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)