You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2008/08/22 14:34:49 UTC

[jira] Commented: (HADOOP-3758) Excessive exceptions in HDFS namenode log file

    [ https://issues.apache.org/jira/browse/HADOOP-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624706#action_12624706 ] 

Hudson commented on HADOOP-3758:
--------------------------------

Integrated in Hadoop-trunk #581 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/581/])

> Excessive exceptions in HDFS namenode log file
> ----------------------------------------------
>
>                 Key: HADOOP-3758
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3758
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.17.1
>            Reporter: Jim Huang
>            Assignee: Lohit Vijayarenu
>            Priority: Blocker
>             Fix For: 0.17.2
>
>         Attachments: HADOOP-3758-17.patch, HADOOP-3758-18.patch, HADOOP-3758-trunk.patch, HADOOP-3758-trunk.patch
>
>
> I upgraded a big cluster, out of which 10 nodes did not get upgraded.  
> The namenode log showed excessive exceptions, causing the namenode log to ate the entire partition space, in this case close to 700GB log file was generated on the namenode.  

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