hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-7382) DataNode in secure mode may throw NullPointerException if client connects before DataNode registers itself with NameNode.
Date Sat, 08 Nov 2014 22:22:33 GMT

     [ https://issues.apache.org/jira/browse/HDFS-7382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Nauroth updated HDFS-7382:
--------------------------------
    Attachment: HDFS-7382.1.patch

We don't really need to rely on NameNode registration.  A DataNode always knows which port
it's listening on for DataTransferProtocol, based solely on its own local configuration. 
The attached patch implements the fix.  I'm still passing through the {{DatanodeID}}, because
that's still useful for debug logging.

> DataNode in secure mode may throw NullPointerException if client connects before DataNode
registers itself with NameNode.
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-7382
>                 URL: https://issues.apache.org/jira/browse/HDFS-7382
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode, security
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>            Priority: Minor
>         Attachments: HDFS-7382.1.patch
>
>
> {{SaslDataTransferServer#receive}} needs to check if the DataNode is listening on a privileged
port.  It does this by checking the address from the {{DatanodeID}}.  However, there is a
window of time when this will be {{null}}.  If a client is still holding a {{LocatedBlock}}
that references that DataNode and chooses to connect, then there is a risk of getting a {{NullPointerException}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message