You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "James Clampffer (JIRA)" <ji...@apache.org> on 2015/12/03 22:36:11 UTC
[jira] [Updated] (HDFS-9504) libhdfs++ Initialize BadNodeTracker in
FileSystemImpl constructor
[ https://issues.apache.org/jira/browse/HDFS-9504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Clampffer updated HDFS-9504:
----------------------------------
Attachment: HDFS-9504.HDFS-8707.000.patch
Attached fix, just adds a BadDataNodeTracker to the member initialization list of FileSystemImpl.
Need to complete HDFS-9489 so this sort of thing doesn't happen again.
> libhdfs++ Initialize BadNodeTracker in FileSystemImpl constructor
> -----------------------------------------------------------------
>
> Key: HDFS-9504
> URL: https://issues.apache.org/jira/browse/HDFS-9504
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs-client
> Reporter: James Clampffer
> Assignee: James Clampffer
> Attachments: HDFS-9504.HDFS-8707.000.patch
>
>
> Without a user supplied NodeExclusionRule reads will always segfault because FileSystemImpl::bad_node_tracker_ never gets initialized.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)