Added IP check compared to host name #36
Conversation
|
some things like the NUC machines have crazy weird networking that may not work with this...need to verify. @tkunicki can you check on a mac? |
|
@nhambletCCRI or @ellisbjohns take a look...seems useful to others... |
conf/cloud-local.conf
Outdated
| @@ -35,6 +35,14 @@ if [[ -z "${CL_BIND_ADDRESS}" ]]; then | |||
| CL_BIND_ADDRESS="127.0.0.1" | |||
| fi | |||
|
|
|||
| # compare the two | |||
| resolved_ip=$(getent hosts $CL_HOSTNAME | awk '{print $1}') | |||
There was a problem hiding this comment.
getent isn't available on BSD, quick search has me stumped for replacement
There was a problem hiding this comment.
hmmm what about another way on a bsd box to get the hostname,ip mappings?
|
Have we done enough testing on the NUCs to confirm that this works? |
|
Should see something like this: instead of localhost.localdomain/127.0.0.1 and it should match as the namenode names... |
|
this is important when running hbase that binds not on 127.x but on the external ip of the box |
This checks to see if the configured hostname and IP resolve to the same address. If not the datanodes don't like it and it won't init...Most common problem is that the people are setting a short name in /etc/hosts or something like that.