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 "John George (JIRA)" <ji...@apache.org> on 2011/05/12 17:02:47 UTC

[jira] [Commented] (HADOOP-7282) getRemoteIp could return null in cases where the call is ongoing but the ip went away.

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

John George commented on HADOOP-7282:
-------------------------------------

Please ignore the "diffs.txt" file - that was accidentally uploaded. Sorry for the confusion .

> getRemoteIp could return null in cases where the call is ongoing but the ip went away.
> --------------------------------------------------------------------------------------
>
>                 Key: HADOOP-7282
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7282
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: John George
>            Assignee: John George
>             Fix For: 0.20.205.0, 0.23.0
>
>         Attachments: HADOOP-7282.patch, diffs.txt
>
>
> getRemoteIp gets the ip from socket instead of the stored ip in Connection object. Thus calls to this function could return null when a client disconnected, but the rpc call is still ongoing...

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