Affects Version/s: None
Fix Version/s: 0.90.0
Amazon EC2 supports Elastic IP Addresses to implement the effect of having a static IP address for public servers running on EC2. Up on hbase-users@ there was some recent discussion, confirmed, that when an EC2 instance queries the external DNS name of an elastic IP address, EC2 DNS returns the internal IP address of the instance to which the elastic IP address is bound, so it is safe to use elastic IPs for the ZK and master nodes. We gain the ability to do transparent replacement of one instance, e.g. failed, with another without incurring any additional cost.
Update launch-hbase-zookeeper and launch-hbase-master to allocate elastic IPs:
and then assign the elastic IP address to the appropriate instance(s):
and then get the external DNS name to use when performing substitutions on master and slave configs:
When shutting down the cluster, just release the elastic IPs after terminating the instances:
NOTE: AWS accounts default to a limit of 5 Elastic IP addresses but most will run with 1 master and 3 or 1 ZK instances. And, the ZK ensemble can be shared.
A follow up issue can address making scripts to launch replacements for failed instances transparently.