[HBASE-24667] Rename configs that support atypical DNS set ups to put them in hbase.unsafe

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0-alpha-1, 2.4.0
• Component/s: conf, Operability
• Labels: beginner
• Hadoop Flags: Reviewed
• Assignee: Prathyusha
• Reporter: Sean Busbey
• Created: 01/Jul/20 17:08
• Updated: 15/Mar/21 09:20
• Resolved: 09/Nov/20 07:16

Description

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:

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.

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.

Issue Links

• is related to: HBASE-25665 Disable reverse DNS lookup for SASL Kerberos client connection
• links to: GitHub Pull Request #2542
• links to: GitHub Pull Request #2632