Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.92.0
-
None
-
Reviewed
Description
This isssue is unlikely to come up in a cluster test case. However, for development, the following thing happens:
1. Start the HBase cluster locally, on network A (DNS A, etc)
2. The region locations are cached using the hostname (mycomputer.company.com, 211.x.y.z - real ip)
3. Change network location (go home)
4. Start the HBase cluster locally. My hostname / ips are not different (mycomputer, 192.168.0.130 - new ip)
If the region locations have been cached using the hostname, there is an UnknownHostException in CatalogTracker.getCachedConnection(ServerName sn), uncaught in the catch statements. The server will crash constantly.
The error should be caught and not rethrown, so that the cached connection expires normally.