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 "Konstantin Shvachko (JIRA)" <ji...@apache.org> on 2006/09/21 00:31:22 UTC

[jira] Created: (HADOOP-553) DataNode and NameNode main() should catch and report exceptions.

DataNode and NameNode main() should catch and report exceptions.
----------------------------------------------------------------

                 Key: HADOOP-553
                 URL: http://issues.apache.org/jira/browse/HADOOP-553
             Project: Hadoop
          Issue Type: Bug
          Components: dfs, mapred
    Affects Versions: 0.6.2
            Reporter: Konstantin Shvachko


Right now we do not know what happened during startup failure,
because there no records in the logs.
I propose to change main() so that it would catch exceptions and 
log them rather then throwing them into std out.
May be the same should be done for the JobTracker.
The TaskTracker.main() catches at least the IOException.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Re: [jira] Created: (HADOOP-553) DataNode and NameNode main() should catch and report exceptions.

Posted by Arkady Borkovsky <ar...@yahoo-inc.com>.
Should this be true (main() calls and reports exceptions) for all 
system components? Especially for user-facing ones like hadoop client?


On Sep 20, 2006, at 3:31 PM, Konstantin Shvachko (JIRA) wrote:

> DataNode and NameNode main() should catch and report exceptions.
> ----------------------------------------------------------------
>
>                  Key: HADOOP-553
>                  URL: http://issues.apache.org/jira/browse/HADOOP-553
>              Project: Hadoop
>           Issue Type: Bug
>           Components: dfs, mapred
>     Affects Versions: 0.6.2
>             Reporter: Konstantin Shvachko
>
>
> Right now we do not know what happened during startup failure,
> because there no records in the logs.
> I propose to change main() so that it would catch exceptions and
> log them rather then throwing them into std out.
> May be the same should be done for the JobTracker.
> The TaskTracker.main() catches at least the IOException.
>
> -- 
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the 
> administrators: 
> http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see: 
> http://www.atlassian.com/software/jira
>
>


[jira] Assigned: (HADOOP-553) DataNode and NameNode main() should catch and report exceptions.

Posted by "Raghu Angadi (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/HADOOP-553?page=all ]

Raghu Angadi reassigned HADOOP-553:
-----------------------------------

    Assignee: Raghu Angadi

> DataNode and NameNode main() should catch and report exceptions.
> ----------------------------------------------------------------
>
>                 Key: HADOOP-553
>                 URL: http://issues.apache.org/jira/browse/HADOOP-553
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred, dfs
>    Affects Versions: 0.6.2
>            Reporter: Konstantin Shvachko
>         Assigned To: Raghu Angadi
>
> Right now we do not know what happened during startup failure,
> because there no records in the logs.
> I propose to change main() so that it would catch exceptions and 
> log them rather then throwing them into std out.
> May be the same should be done for the JobTracker.
> The TaskTracker.main() catches at least the IOException.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (HADOOP-553) DataNode and NameNode main() should catch and report exceptions.

Posted by "Raghu Angadi (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/HADOOP-553?page=all ]

Raghu Angadi updated HADOOP-553:
--------------------------------

    Attachment:     (was: logging-exceptions.patch)

> DataNode and NameNode main() should catch and report exceptions.
> ----------------------------------------------------------------
>
>                 Key: HADOOP-553
>                 URL: http://issues.apache.org/jira/browse/HADOOP-553
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred, dfs
>    Affects Versions: 0.6.1
>            Reporter: Konstantin Shvachko
>         Assigned To: Raghu Angadi
>
> Right now we do not know what happened during startup failure,
> because there no records in the logs.
> I propose to change main() so that it would catch exceptions and 
> log them rather then throwing them into std out.
> May be the same should be done for the JobTracker.
> The TaskTracker.main() catches at least the IOException.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (HADOOP-553) DataNode and NameNode main() should catch and report exceptions.

Posted by "Raghu Angadi (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/HADOOP-553?page=all ]

Raghu Angadi updated HADOOP-553:
--------------------------------

    Attachment: logging-exceptions-2.patch


merged two seperate patches into one.

> DataNode and NameNode main() should catch and report exceptions.
> ----------------------------------------------------------------
>
>                 Key: HADOOP-553
>                 URL: http://issues.apache.org/jira/browse/HADOOP-553
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred, dfs
>    Affects Versions: 0.6.1
>            Reporter: Konstantin Shvachko
>         Assigned To: Raghu Angadi
>         Attachments: logging-exceptions-2.patch
>
>
> Right now we do not know what happened during startup failure,
> because there no records in the logs.
> I propose to change main() so that it would catch exceptions and 
> log them rather then throwing them into std out.
> May be the same should be done for the JobTracker.
> The TaskTracker.main() catches at least the IOException.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (HADOOP-553) DataNode and NameNode main() should catch and report exceptions.

Posted by "Raghu Angadi (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/HADOOP-553?page=all ]

Raghu Angadi updated HADOOP-553:
--------------------------------

    Attachment: logging-exceptions.patch

logging-exceptions.patch:
Patch to write exceptions to log file instead of stderr. 

I will submit a seperate patch to rotate .out files.


> DataNode and NameNode main() should catch and report exceptions.
> ----------------------------------------------------------------
>
>                 Key: HADOOP-553
>                 URL: http://issues.apache.org/jira/browse/HADOOP-553
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred, dfs
>    Affects Versions: 0.6.2
>            Reporter: Konstantin Shvachko
>         Assigned To: Raghu Angadi
>         Attachments: logging-exceptions.patch
>
>
> Right now we do not know what happened during startup failure,
> because there no records in the logs.
> I propose to change main() so that it would catch exceptions and 
> log them rather then throwing them into std out.
> May be the same should be done for the JobTracker.
> The TaskTracker.main() catches at least the IOException.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (HADOOP-553) DataNode and NameNode main() should catch and report exceptions.

Posted by "Raghu Angadi (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/HADOOP-553?page=all ]

Raghu Angadi updated HADOOP-553:
--------------------------------

    Attachment: stdout-rotate.patch


This patch rotates and keeps last 5 ".out" files created in hadoop-daemon.sh.




> DataNode and NameNode main() should catch and report exceptions.
> ----------------------------------------------------------------
>
>                 Key: HADOOP-553
>                 URL: http://issues.apache.org/jira/browse/HADOOP-553
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred, dfs
>    Affects Versions: 0.6.1
>            Reporter: Konstantin Shvachko
>         Assigned To: Raghu Angadi
>         Attachments: logging-exceptions.patch, stdout-rotate.patch
>
>
> Right now we do not know what happened during startup failure,
> because there no records in the logs.
> I propose to change main() so that it would catch exceptions and 
> log them rather then throwing them into std out.
> May be the same should be done for the JobTracker.
> The TaskTracker.main() catches at least the IOException.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (HADOOP-553) DataNode and NameNode main() should catch and report exceptions.

Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/HADOOP-553?page=all ]

Doug Cutting updated HADOOP-553:
--------------------------------

           Status: Resolved  (was: Patch Available)
    Fix Version/s: 0.8.0
       Resolution: Fixed

I just committed this.  Thanks, Raghu!

> DataNode and NameNode main() should catch and report exceptions.
> ----------------------------------------------------------------
>
>                 Key: HADOOP-553
>                 URL: http://issues.apache.org/jira/browse/HADOOP-553
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs, mapred
>    Affects Versions: 0.6.1
>            Reporter: Konstantin Shvachko
>         Assigned To: Raghu Angadi
>             Fix For: 0.8.0
>
>         Attachments: logging-exceptions-2.patch
>
>
> Right now we do not know what happened during startup failure,
> because there no records in the logs.
> I propose to change main() so that it would catch exceptions and 
> log them rather then throwing them into std out.
> May be the same should be done for the JobTracker.
> The TaskTracker.main() catches at least the IOException.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (HADOOP-553) DataNode and NameNode main() should catch and report exceptions.

Posted by "Raghu Angadi (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/HADOOP-553?page=all ]

Raghu Angadi updated HADOOP-553:
--------------------------------

               Status: Patch Available  (was: Open)
    Affects Version/s: 0.6.1
                           (was: 0.6.2)

> DataNode and NameNode main() should catch and report exceptions.
> ----------------------------------------------------------------
>
>                 Key: HADOOP-553
>                 URL: http://issues.apache.org/jira/browse/HADOOP-553
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred, dfs
>    Affects Versions: 0.6.1
>            Reporter: Konstantin Shvachko
>         Assigned To: Raghu Angadi
>         Attachments: logging-exceptions.patch, stdout-rotate.patch
>
>
> Right now we do not know what happened during startup failure,
> because there no records in the logs.
> I propose to change main() so that it would catch exceptions and 
> log them rather then throwing them into std out.
> May be the same should be done for the JobTracker.
> The TaskTracker.main() catches at least the IOException.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (HADOOP-553) DataNode and NameNode main() should catch and report exceptions.

Posted by "Raghu Angadi (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/HADOOP-553?page=all ]

Raghu Angadi updated HADOOP-553:
--------------------------------

    Attachment:     (was: stdout-rotate.patch)

> DataNode and NameNode main() should catch and report exceptions.
> ----------------------------------------------------------------
>
>                 Key: HADOOP-553
>                 URL: http://issues.apache.org/jira/browse/HADOOP-553
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred, dfs
>    Affects Versions: 0.6.1
>            Reporter: Konstantin Shvachko
>         Assigned To: Raghu Angadi
>
> Right now we do not know what happened during startup failure,
> because there no records in the logs.
> I propose to change main() so that it would catch exceptions and 
> log them rather then throwing them into std out.
> May be the same should be done for the JobTracker.
> The TaskTracker.main() catches at least the IOException.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira