[ https://issues.apache.org/jira/browse/HDFS-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jakob Homan updated HDFS-1150: ------------------------------ Attachment: HDFS-1150-BF-Y20-LOG-DIRS-2.patch Our Ops noticed the new jsvc pushes the classpath so long they can no longer monitor the class name, so adding in a fake env variable to identify the started process.... > Verify datanodes' identities to clients in secure clusters > ---------------------------------------------------------- > > Key: HDFS-1150 > URL: https://issues.apache.org/jira/browse/HDFS-1150 > Project: Hadoop HDFS > Issue Type: New Feature > Components: data-node > Affects Versions: 0.22.0 > Reporter: Jakob Homan > Assignee: Jakob Homan > Attachments: commons-daemon-1.0.2-src.tar.gz, > HDFS-1150-BF-Y20-LOG-DIRS-2.patch, HDFS-1150-BF-Y20-LOG-DIRS.patch, > HDFS-1150-BF1-Y20.patch, hdfs-1150-bugfix-1.1.patch, > hdfs-1150-bugfix-1.2.patch, hdfs-1150-bugfix-1.patch, > HDFS-1150-y20.build-script.patch, HDFS-1150-Y20S-ready-5.patch, > HDFS-1150-Y20S-ready-6.patch, HDFS-1150-Y20S-ready-7.patch, > HDFS-1150-Y20S-ready-8.patch, HDFS-1150-Y20S-Rough-2.patch, > HDFS-1150-Y20S-Rough-3.patch, HDFS-1150-Y20S-Rough-4.patch, > HDFS-1150-Y20S-Rough.txt > > > Currently we use block access tokens to allow datanodes to verify clients' > identities, however we don't have a way for clients to verify the > authenticity of the datanodes themselves. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.