[
https://issues.apache.org/jira/browse/HADOOP-15336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16418039#comment-16418039
]
Rushabh S Shah commented on HADOOP-15336:
-----------------------------------------
Thanks [~zhengxg3] for the stack trace.
The stack trace shows that the router(acting as client) got an NPE from
namenode.
I am not familiar with RouterRpcServer so I apologize in advance if I sound
confused.
But why does router decodes the protobuf response and then encodes again ?
Why can't router just relays the response from namenode without decoding and
re-encoding ?
IIUC now I have to think about backwards compatibility w.r.t to dfs client,
namenode *and router* even if majority of people don't use router feature ?
IMO this shouldn't be flagged as backwards incompatible.
> NPE for FsServerDefaults.getKeyProviderUri() for clientProtocol communication
> between 2.7 and 3.2
> -------------------------------------------------------------------------------------------------
>
> Key: HADOOP-15336
> URL: https://issues.apache.org/jira/browse/HADOOP-15336
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 3.1.0, 3.2.0
> Reporter: Sherwood Zheng
> Assignee: Sherwood Zheng
> Priority: Major
> Labels: backward-incompatible, common
> Attachments: HADOOP-15336.000.patch, HADOOP-15336.001.patch
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
