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 "Yufeng Jiang (JIRA)" <ji...@apache.org> on 2016/02/17 06:30:18 UTC
[jira] [Commented] (HADOOP-12811) Change kms server port number
which conflicts with HMaster port number
[ https://issues.apache.org/jira/browse/HADOOP-12811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149910#comment-15149910 ]
Yufeng Jiang commented on HADOOP-12811:
---------------------------------------
Stating from HBase 0.99, HMaster's port number was set to 16000 to avoid the conflict with linux ephemeral port. At roughly same time, hadoop kms was released. As pointed out by jmhsieh@
"Timeline wise, the changes were released at roughly same time – This change was in a released by hbase in 30/oct/2014 [1] and in hadoop 18/nov/2014 [2].
[1] https://archive.apache.org/dist/hbase/hbase-0.99.0/
[2] http://hadoop.apache.org/releases.html
"
> Change kms server port number which conflicts with HMaster port number
> ----------------------------------------------------------------------
>
> Key: HADOOP-12811
> URL: https://issues.apache.org/jira/browse/HADOOP-12811
> Project: Hadoop Common
> Issue Type: Improvement
> Components: kms
> Affects Versions: 2.6.1, 2.7.0, 2.7.1, 2.7.2, 2.6.2, 2.6.3
> Reporter: Yufeng Jiang
> Labels: patch
>
> The HBase's HMaster port number conflicts with Hadoop kms port number. Both uses 16000.
> There might be use cases user need kms and HBase present on the same cluster. The HBase is able to encrypt its HFiles but user might need KMS to encrypt other HDFS directories.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)