[
https://issues.apache.org/jira/browse/HBASE-2864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12891352#action_12891352
]
stack commented on HBASE-2864:
------------------------------
@Mathias J-D is right. See HBASE-2599. In there, whatever the master figures
for regionserver name, thats what it'll use in all subsequent communication
(Only master does hostname lookup now where before RS and Master did it making
for possibility of disagreement). There is a 0.20 patch in the issue if you
want to patch your 0.20.x.
if above is satisfactory, please resolve the issue.
> HBase handling of host names is case sensitive
> ----------------------------------------------
>
> Key: HBASE-2864
> URL: https://issues.apache.org/jira/browse/HBASE-2864
> Project: HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 0.20.5, 0.89.20100621
> Environment: Linux
> Reporter: Mathias Herberts
> Priority: Critical
> Fix For: 0.90.0
>
>
> Our HBase cluster showed weird multiple assigments of all regions.
> Master logs showed that every minute region assignments were all determined
> invalid and regions were being re-assigned.
> The reason for the assignements to be found invalid is that they were done on
> hosts whose name in /etc/hosts was in lowercase but whose name in the DNS was
> in uppercase.
> In BaseScanner.java:572, the HServerInfo is retrieved using the servername as
> key. As the name comes from the DNS, it was all uppercase and thus no
> HServerInfo could be found.
> The DNS cache needs to have its keys converted to lowercase to avoid this
> (HServerInfo.java:245).
> This is a major problem because simple changes to the DNS infrastructure can
> cause major data corruption in HBase.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
