Need better Hyperspace error message on bad replica host names

[GoogleCodeExporter]

Groupon had an issue where they copied a hypertable.cfg file from one cluster 
to the other.  When they started, Hyperspace failed because the replica names 
were for hosts that were not visible in the new environment.  It generated the 
following error message:

1332876291 FATAL Hyperspace.Master : 
(/home/herbert/src-hypertable/src/cc/Hyperspace/BerkeleyDbFilesystem.cc:341) 
Error initializing Berkeley DB 
(dir=/packages/encap/hypertable-0.9.5.6p1/lib/hypertable/0.9.5.6/hyperspace) - 
DbEnv::repmgr_start: Invalid argument

This error message was not very informative and took us a while to figure out 
what had happened.  It would be better if this error message included 
information about the arguments (e.g. host names of replicas) that it 
considered invalid.

Original issue reported on code.google.com by nuggetwh...@gmail.com on 29 Mar 2012 at 11:09

[GoogleCodeExporter]

BDB has a function to retrieve a list of all servers and their status 
(disconnected/connected). But in my tests this server list is empty if you 
specify an unknown hostname. 

If there's an exception and that list is not empty then i am printing it to the 
log. In any case there's a more general error message now ("please make sure 
that the hyperspace replicas are correctly configured"). 

Original comment by ch...@crupp.de on 30 Mar 2012 at 6:08

• Changed state: Fixed