You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Jitendra Nath Pandey (JIRA)" <ji...@apache.org> on 2009/10/29 21:39:59 UTC

[jira] Created: (HADOOP-6343) Stack trace of any runtime exceptions should be recorded in the server logs.

Stack trace of any runtime exceptions should be recorded in the server logs. 
-----------------------------------------------------------------------------

                 Key: HADOOP-6343
                 URL: https://issues.apache.org/jira/browse/HADOOP-6343
             Project: Hadoop Common
          Issue Type: Improvement
            Reporter: Jitendra Nath Pandey
            Assignee: Jitendra Nath Pandey


Hadoop RPC catches any server side exception and throws an IOException. Runtime excpetions should be recorded in the server logs before being thrown as IOException.

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


[jira] Updated: (HADOOP-6343) Stack trace of any runtime exceptions should be recorded in the server logs.

Posted by "Jitendra Nath Pandey (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jitendra Nath Pandey updated HADOOP-6343:
-----------------------------------------

    Attachment: HADOOP-6343.1.patch

> Stack trace of any runtime exceptions should be recorded in the server logs. 
> -----------------------------------------------------------------------------
>
>                 Key: HADOOP-6343
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6343
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Jitendra Nath Pandey
>            Assignee: Jitendra Nath Pandey
>         Attachments: HADOOP-6343.1.patch
>
>
> Hadoop RPC catches any server side exception and throws an IOException. Runtime excpetions should be recorded in the server logs before being thrown as IOException.

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


[jira] Commented: (HADOOP-6343) Stack trace of any runtime exceptions should be recorded in the server logs.

Posted by "Tsz Wo (Nicholas), SZE (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772612#action_12772612 ] 

Tsz Wo (Nicholas), SZE commented on HADOOP-6343:
------------------------------------------------

I suggest committing this to 0.20.  Otherwise, it is hard to fix bugs like HDFS-626.

> Stack trace of any runtime exceptions should be recorded in the server logs. 
> -----------------------------------------------------------------------------
>
>                 Key: HADOOP-6343
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6343
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>            Reporter: Jitendra Nath Pandey
>            Assignee: Jitendra Nath Pandey
>         Attachments: HADOOP-6343.1.patch, HADOOP-6343.2.patch
>
>
> Hadoop RPC catches any server side exception and throws an IOException. Runtime excpetions should be recorded in the server logs before being thrown as IOException.

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


[jira] Updated: (HADOOP-6343) Stack trace of any runtime exceptions should be recorded in the server logs.

Posted by "Tsz Wo (Nicholas), SZE (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tsz Wo (Nicholas), SZE updated HADOOP-6343:
-------------------------------------------

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

Unfortunately, this improvement is not qualified to be committed to 0.20.

I have committed this to 0.21 and above.  Thanks, Jitendra!

> Stack trace of any runtime exceptions should be recorded in the server logs. 
> -----------------------------------------------------------------------------
>
>                 Key: HADOOP-6343
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6343
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>            Reporter: Jitendra Nath Pandey
>            Assignee: Jitendra Nath Pandey
>             Fix For: 0.21.0, 0.22.0
>
>         Attachments: HADOOP-6343.1.patch, HADOOP-6343.2.patch
>
>
> Hadoop RPC catches any server side exception and throws an IOException. Runtime excpetions should be recorded in the server logs before being thrown as IOException.

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


[jira] Commented: (HADOOP-6343) Stack trace of any runtime exceptions should be recorded in the server logs.

Posted by "Jitendra Nath Pandey (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772609#action_12772609 ] 

Jitendra Nath Pandey commented on HADOOP-6343:
----------------------------------------------

This change adds stack-trace to the server logs. Since the change is only in log message, no additional unit tests are required.

> Stack trace of any runtime exceptions should be recorded in the server logs. 
> -----------------------------------------------------------------------------
>
>                 Key: HADOOP-6343
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6343
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>            Reporter: Jitendra Nath Pandey
>            Assignee: Jitendra Nath Pandey
>         Attachments: HADOOP-6343.1.patch, HADOOP-6343.2.patch
>
>
> Hadoop RPC catches any server side exception and throws an IOException. Runtime excpetions should be recorded in the server logs before being thrown as IOException.

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


[jira] Updated: (HADOOP-6343) Stack trace of any runtime exceptions should be recorded in the server logs.

Posted by "Jitendra Nath Pandey (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jitendra Nath Pandey updated HADOOP-6343:
-----------------------------------------

    Status: Patch Available  (was: Open)

HADOOP-6343.2.patch is submitted for hudson tests.

> Stack trace of any runtime exceptions should be recorded in the server logs. 
> -----------------------------------------------------------------------------
>
>                 Key: HADOOP-6343
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6343
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Jitendra Nath Pandey
>            Assignee: Jitendra Nath Pandey
>         Attachments: HADOOP-6343.1.patch, HADOOP-6343.2.patch
>
>
> Hadoop RPC catches any server side exception and throws an IOException. Runtime excpetions should be recorded in the server logs before being thrown as IOException.

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


[jira] Commented: (HADOOP-6343) Stack trace of any runtime exceptions should be recorded in the server logs.

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772818#action_12772818 ] 

Hudson commented on HADOOP-6343:
--------------------------------

Integrated in Hadoop-Common-trunk-Commit #80 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Common-trunk-Commit/80/])
    . Log unexpected throwable object caught in RPC.  Contributed by Jitendra Nath Pandey


> Stack trace of any runtime exceptions should be recorded in the server logs. 
> -----------------------------------------------------------------------------
>
>                 Key: HADOOP-6343
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6343
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>            Reporter: Jitendra Nath Pandey
>            Assignee: Jitendra Nath Pandey
>         Attachments: HADOOP-6343.1.patch, HADOOP-6343.2.patch
>
>
> Hadoop RPC catches any server side exception and throws an IOException. Runtime excpetions should be recorded in the server logs before being thrown as IOException.

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


[jira] Updated: (HADOOP-6343) Stack trace of any runtime exceptions should be recorded in the server logs.

Posted by "Jitendra Nath Pandey (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jitendra Nath Pandey updated HADOOP-6343:
-----------------------------------------

    Attachment: HADOOP-6343.0-20.patch

Patch for hadoop-20 is added.

> Stack trace of any runtime exceptions should be recorded in the server logs. 
> -----------------------------------------------------------------------------
>
>                 Key: HADOOP-6343
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6343
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>            Reporter: Jitendra Nath Pandey
>            Assignee: Jitendra Nath Pandey
>             Fix For: 0.21.0, 0.22.0
>
>         Attachments: HADOOP-6343.0-20.patch, HADOOP-6343.1.patch, HADOOP-6343.2.patch
>
>
> Hadoop RPC catches any server side exception and throws an IOException. Runtime excpetions should be recorded in the server logs before being thrown as IOException.

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


[jira] Updated: (HADOOP-6343) Stack trace of any runtime exceptions should be recorded in the server logs.

Posted by "Jitendra Nath Pandey (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jitendra Nath Pandey updated HADOOP-6343:
-----------------------------------------

    Attachment: HADOOP-6343.2.patch

> Stack trace of any runtime exceptions should be recorded in the server logs. 
> -----------------------------------------------------------------------------
>
>                 Key: HADOOP-6343
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6343
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Jitendra Nath Pandey
>            Assignee: Jitendra Nath Pandey
>         Attachments: HADOOP-6343.1.patch, HADOOP-6343.2.patch
>
>
> Hadoop RPC catches any server side exception and throws an IOException. Runtime excpetions should be recorded in the server logs before being thrown as IOException.

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


[jira] Commented: (HADOOP-6343) Stack trace of any runtime exceptions should be recorded in the server logs.

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772182#action_12772182 ] 

Hadoop QA commented on HADOOP-6343:
-----------------------------------

+1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12423735/HADOOP-6343.2.patch
  against trunk revision 831478.

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs warnings.

    +1 release audit.  The applied patch does not increase the total number of release audit warnings.

    +1 core tests.  The patch passed core unit tests.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/121/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/121/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/121/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/121/console

This message is automatically generated.

> Stack trace of any runtime exceptions should be recorded in the server logs. 
> -----------------------------------------------------------------------------
>
>                 Key: HADOOP-6343
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6343
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>            Reporter: Jitendra Nath Pandey
>            Assignee: Jitendra Nath Pandey
>         Attachments: HADOOP-6343.1.patch, HADOOP-6343.2.patch
>
>
> Hadoop RPC catches any server side exception and throws an IOException. Runtime excpetions should be recorded in the server logs before being thrown as IOException.

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


[jira] Updated: (HADOOP-6343) Stack trace of any runtime exceptions should be recorded in the server logs.

Posted by "Tsz Wo (Nicholas), SZE (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tsz Wo (Nicholas), SZE updated HADOOP-6343:
-------------------------------------------

     Component/s: ipc
    Hadoop Flags: [Reviewed]

+1 patch looks good.

> Stack trace of any runtime exceptions should be recorded in the server logs. 
> -----------------------------------------------------------------------------
>
>                 Key: HADOOP-6343
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6343
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>            Reporter: Jitendra Nath Pandey
>            Assignee: Jitendra Nath Pandey
>         Attachments: HADOOP-6343.1.patch, HADOOP-6343.2.patch
>
>
> Hadoop RPC catches any server side exception and throws an IOException. Runtime excpetions should be recorded in the server logs before being thrown as IOException.

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


[jira] Commented: (HADOOP-6343) Stack trace of any runtime exceptions should be recorded in the server logs.

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12773022#action_12773022 ] 

Hudson commented on HADOOP-6343:
--------------------------------

Integrated in Hadoop-Common-trunk #147 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Common-trunk/147/])
    . Log unexpected throwable object caught in RPC.  Contributed by Jitendra Nath Pandey


> Stack trace of any runtime exceptions should be recorded in the server logs. 
> -----------------------------------------------------------------------------
>
>                 Key: HADOOP-6343
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6343
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>            Reporter: Jitendra Nath Pandey
>            Assignee: Jitendra Nath Pandey
>             Fix For: 0.21.0, 0.22.0
>
>         Attachments: HADOOP-6343.1.patch, HADOOP-6343.2.patch
>
>
> Hadoop RPC catches any server side exception and throws an IOException. Runtime excpetions should be recorded in the server logs before being thrown as IOException.

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


[jira] Updated: (HADOOP-6343) Stack trace of any runtime exceptions should be recorded in the server logs.

Posted by "Robert Chansler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Chansler updated HADOOP-6343:
------------------------------------

    Release Note: Record runtime exceptions in server log to facilitate fault analysis.

> Stack trace of any runtime exceptions should be recorded in the server logs. 
> -----------------------------------------------------------------------------
>
>                 Key: HADOOP-6343
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6343
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>            Reporter: Jitendra Nath Pandey
>            Assignee: Jitendra Nath Pandey
>             Fix For: 0.21.0, 0.22.0
>
>         Attachments: HADOOP-6343.0-20.patch, HADOOP-6343.1.patch, HADOOP-6343.2.patch
>
>
> Hadoop RPC catches any server side exception and throws an IOException. Runtime excpetions should be recorded in the server logs before being thrown as IOException.

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