Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <198282.1182476906250.JavaMail.jira@brutus>
Date: Thu, 21 Jun 2007 18:48:26 -0700 (PDT)
From: "Nigel Daley (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-1520) IndexOutOfBoundsException in
 FSEditLog.processIOError
In-Reply-To: <28034189.1182476785857.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507091 ] 

Nigel Daley commented on HADOOP-1520:
-------------------------------------

It might be significant that the namenode is rolling the fsimage file right before the IndexOutOfBoundsException.

> IndexOutOfBoundsException in FSEditLog.processIOError
> -----------------------------------------------------
>
>                 Key: HADOOP-1520
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1520
>             Project: Hadoop
>          Issue Type: Bug
>    Affects Versions: 0.14.0
>            Reporter: Nigel Daley
>            Assignee: Konstantin Shvachko
>
> Running NNBench I saw these exceptions in the NameNode logs:
> NAMENODE:
> 2007-06-21 04:02:53,587 INFO org.apache.hadoop.fs.FSNamesystem: Roll FSImage
> 2007-06-21 04:02:53,594 INFO org.apache.hadoop.ipc.Server: IPC Server handler 0 on 8020, call complete(/user/hadoopqa/nameNode100Benchmark/output/.214.crc, DFSClient_-1646448212) from 72.30.51.75:56245: error: java.io.IOException: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
> java.io.IOException: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
>         at java.util.ArrayList.RangeCheck(ArrayList.java:547)
>         at java.util.ArrayList.remove(ArrayList.java:387)
>         at org.apache.hadoop.dfs.FSEditLog.processIOError(FSEditLog.java:169)
>         at org.apache.hadoop.dfs.FSEditLog.logSync(FSEditLog.java:407)
>         at org.apache.hadoop.dfs.FSNamesystem.completeFile(FSNamesystem.java:878)
>         at org.apache.hadoop.dfs.NameNode.complete(NameNode.java:346)
>         at sun.reflect.GeneratedMethodAccessor16.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:340)
>         at org.apache.hadoop.ipc.Server$Handler.run(Server.java:566)
> ...
> 2007-06-21 04:02:53,823 WARN org.apache.hadoop.dfs.StateChange: DIR* NameSystem.completeFile: failed to complete /user/hadoopqa/nameNode100Benchmark/output/.214.crc because dir.getFileBlocks() is non-null and pendingFile is null
> 2007-06-21 04:02:53,828 INFO org.apache.hadoop.ipc.Server: IPC Server handler 14 on 8020, call complete(/user/hadoopqa/nameNode100Benchmark/output/.214.crc, DFSClient_-1646448212) from 72.30.51.75:56245: error: java.io.IOException: Could not complete write to file /user/hadoopqa/nameNode100Benchmark/output/.214.crc by DFSClient_-1646448212
> java.io.IOException: Could not complete write to file /user/hadoopqa/nameNode100Benchmark/output/.214.crc by DFSClient_-1646448212
>         at org.apache.hadoop.dfs.NameNode.complete(NameNode.java:352)
>         at sun.reflect.GeneratedMethodAccessor16.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:340)
>         at org.apache.hadoop.ipc.Server$Handler.run(Server.java:566)
> This last exception occurs over and over again forever (this could be a result of the way NNBench is written).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.