accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-2227) Concurrent randomwalk fails when namenode dies after bulk import step
Date Wed, 22 Jan 2014 15:43:26 GMT


Sean Busbey commented on ACCUMULO-2227:

I think it'd be fine to put a note in the README for randomwalk that if you're going to test
HA failover, you should expect some failures like this if you are using an HDFS version prior
to 2.1.0. should also include a link to HADOOP-9792 for more details.

Since our recommended version for Hadoop 2 is 2.2.0, I think that'd be fine. AFAIK, our non-test
code already has retries built in for when we need to delete something (e.g. the GC).

> Concurrent randomwalk fails when namenode dies after bulk import step
> ---------------------------------------------------------------------
>                 Key: ACCUMULO-2227
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 1.4.4
>            Reporter: Bill Havanki
>              Labels: ha, randomwalk, test
> Running Concurrent randomwalk under HDFS HA, if the active namenode is killed:
> {noformat}
> 20 12:27:51,119 [retry.RetryInvocationHandler] WARN : Exception while invoking class
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.delete. Not retrying
because the invoked method is not idempotent, and unable to determine whether it was invoked
> Failed on local exception: Response is null.;
Host Details : local host is: ""; destination host is: "":8020;
> ...
>  at org.apache.hadoop.hdfs.DFSClient.delete(
> at org.apache.hadoop.hdfs.DistributedFileSystem.delete(
> at org.apache.accumulo.server.test.randomwalk.concurrent.BulkImport.visit(
> ...
> Caused by: Response is null.
> at org.apache.hadoop.ipc.Client$Connection.receiveResponse(
> at org.apache.hadoop.ipc.Client$
> {noformat}
> This arises from an HDFS path delete call that cleans up from the bulk import. The test
should be resilient here (and when the paths are made earlier in the test) so that the test
can continue once failover has completed.

This message was sent by Atlassian JIRA

View raw message