[
https://issues.apache.org/jira/browse/HBASE-30257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18093040#comment-18093040
]
Hudson commented on HBASE-30257:
--------------------------------
Results for branch master
[build #1469 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1469/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1469/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1469/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
> Fix case-sensitive hostname check in region server
> --------------------------------------------------
>
> Key: HBASE-30257
> URL: https://issues.apache.org/jira/browse/HBASE-30257
> Project: HBase
> Issue Type: Bug
> Affects Versions: 3.0.0-beta-1, 4.0.0-alpha-1, 2.6.6
> Reporter: Tak-Lon (Stephen) Wu
> Assignee: Tak-Lon (Stephen) Wu
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0-alpha-1
>
>
> HBASE-27333 introduced a hostname validation check on RegionServer startup.
> This check is case-sensitive; if the Master reports the hostname in uppercase
> but the RegionServer resolves it in lowercase, the RegionServer aborts with a
> hostname mismatch error. This occurs even though DNS resolution is
> case-insensitive by nature and both names refer to the same host
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
