[
https://issues.apache.org/jira/browse/HADOOP-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated HADOOP-7346:
--------------------------------
Attachment: hadoop-7346.txt
I couldn't think of any way to do it with mocks, so I did brute force and wrote
some tests which just replay RPC traces that I captured by hand from 0.18.3,
branch-0.20, and 0.21.0. They then verify that the response matches my captured
response (which I verified generated a reasonable exception on the client)
> 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
>
>
> 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
