hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7346) Send back nicer error to clients using outdated IPC version
Date Fri, 03 Jun 2011 21:53:47 GMT

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

Todd Lipcon commented on HADOOP-7346:

I'd like to commit this to 0.22 branch, since it really helps with version transitions, and
I think 0.22 should see more uptake than 0.21 did.

It applies cleanly, the only issue is that it requires guava as a dependency in the tests.
Anyone have an issue with my adding it to ivy? The other option is to not include the tests
in the commit (or reimplement the two methods we need). Adding guava seems easiest and will
also make it easier to backport other patches from trunk which might use it, so that' my preference.

> Send back nicer error to clients using outdated IPC version
> -----------------------------------------------------------
>                 Key: HADOOP-7346
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7346
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>    Affects Versions: 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>             Fix For: 0.22.0
>         Attachments: hadoop-7346.txt, hadoop-7346.txt, hadoop-7346.txt
> When an older Hadoop version tries to contact a newer Hadoop version across an IPC protocol
version bump, the client currently just gets a non-useful error message like "EOFException".
> Instead, the IPC server code can speak just enough of prior IPC protocols to send back
a "fatal" message indicating the version mismatch.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message