[ 
https://issues.apache.org/jira/browse/HBASE-24667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17228745#comment-17228745
 ] 

Hudson commented on HBASE-24667:
--------------------------------

Results for branch branch-2
        [build #97 on 
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/97/]:
 (/) *{color:green}+1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/97/General_20Nightly_20Build_20Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/97/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/97/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/97/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Rename configs that support atypical DNS set ups to put them in hbase.unsafe
> ----------------------------------------------------------------------------
>
>                 Key: HBASE-24667
>                 URL: https://issues.apache.org/jira/browse/HBASE-24667
>             Project: HBase
>          Issue Type: Task
>          Components: conf, Operability
>            Reporter: Sean Busbey
>            Assignee: Prathyusha
>            Priority: Major
>              Labels: beginner
>             Fix For: 3.0.0-alpha-1, 2.4.0
>
>
> HBASE-18226 added a config for disabling reverse DNS checks 
> {{hbase.regionserver.hostname.disable.master.reversedns}} and the release 
> note calls out that the config is dangerous:
> {quote}he following config is added by this JIRA:
> hbase.regionserver.hostname.disable.master.reversedns
> This config is for experts: don't set its value unless you really know what 
> you are doing.
>  When set to true, regionserver will use the current node hostname for the 
> servername and HMaster will skip reverse DNS lookup and use the hostname sent 
> by regionserver instead. Note that this config and 
> hbase.regionserver.hostname are mutually exclusive. See 
> https://issues.apache.org/jira/browse/HBASE-18226 for more details.
> Caution: please make sure rolling upgrade succeeds before turning on this 
> feature.
> {quote}
> We should make clear the risks of using this config by making sure the name 
> starts with {{hbase.unsafe}}.
> Rename {{hbase.regionserver.hostname.disable.master.reversedns}} to 
> {{hbase.unsafe.regionserver.hostname.disable.master.reversedns}} but make 
> sure the former is kept with a "deprecated config name" warning.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to