hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kihwal Lee (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7505) EOFException in RPC stack should have a nicer error message
Date Wed, 09 Nov 2011 15:39:52 GMT

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

Kihwal Lee commented on HADOOP-7505:

In branch-0.20-security, I've seen clients getting an EOFException when the connection was
closed in the middle of an RPC transaction. I am guessing this is because the input stream
was broken while reading a response. It makes a perfect sense at that level, but showing that
to users who are reading a file can be quite confusing. I haven't checked whether the trunk
also has this issue.
> EOFException in RPC stack should have a nicer error message
> -----------------------------------------------------------
>                 Key: HADOOP-7505
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7505
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>    Affects Versions: 0.23.0
>            Reporter: Eli Collins
>            Assignee: Harsh J
>            Priority: Minor
> Lots of user logs involve a user running mismatched versions, and for some reason or
another, they get EOFException instead of a proper version mismatch exception. We should be
able to catch this at appropriate points, and have a nicer exception message explaining that
it's a possible version mismatch, or that they're trying to connect to the incorrect port.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message