[ https://issues.apache.org/jira/browse/HDFS-15148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17027899#comment-17027899 ]
Konstantin Shvachko edited comment on HDFS-15148 at 2/1/20 12:08 AM: --------------------------------------------------------------------- This looks reasonable. Would make sense to # fix checkstyle warning with some unused imports # Remove {{Thread.sleep( * );}} before the loop. I see 3 occasions of those. You shouldn't need them anymore. was (Author: shv): This looks reasonable. Would make sense to # fix checkstyle warning with some unused imports # Remove {{Thread.sleep(*);}} before the loop. I see 3 occasions of those. You shouldn't need them anymore. > dfs.namenode.send.qop.enabled should not apply to primary NN port > ----------------------------------------------------------------- > > Key: HDFS-15148 > URL: https://issues.apache.org/jira/browse/HDFS-15148 > Project: Hadoop HDFS > Issue Type: Bug > Affects Versions: 2.10.1, 3.3.1 > Reporter: Chen Liang > Assignee: Chen Liang > Priority: Major > Attachments: HDFS-15148.001.patch, HDFS-15148.002.patch, > HDFS-15148.003.patch > > > In HDFS-13617, NameNode can be configured to wrap its established QOP into > block access token as an encrypted message. Later on DataNode will use this > message to create SASL connection. But this new behavior should only apply to > new auxiliary NameNode ports, not the primary port (the one configured in > fs.defaultFS), as it may cause conflicting behavior with existing other SASL > related configuration (e.g. dfs.data.transfer.protection). Since this > configure is introduced for to auxiliary ports only, we should restrict this > new behavior to not apply to primary port. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org