Member since
10-17-2016
3
Posts
1
Kudos Received
0
Solutions
10-20-2016
02:30 AM
1 Kudo
Tested now: it works! But we prefer to adopt a plain network config to avoid issues in the future.
... View more
10-19-2016
07:21 AM
Interesting! There is only the overhead to mantain a hosts file. A real problem is that Cloudera doesn't support multihomed conifigs 😞
... View more
10-19-2016
03:35 AM
Hi, we got some issues while planning a secure Cloudera cluster. The situation is as follows: - All host are multihomed, i.e. they have two separate IP addresses connected to two separate LANs. One is intended for interaction with the enterprise network and one for intra-cluster traffic. The intra-cluster network is not accessible from the outside. - Each IP-address is associated with a separate hostname, e.g. host-internal.domain.com and host-enterprise.domain.com. The internal hostname is used as primary hostname and used in all Hadoop configurations. - The DNS does resolve the hostnames consistent in all networks. There is no way to resolve the same hostname different depending on the network you are in. Now I'm planning to set up Kerberos with an AD, that is placed in the enterprise network. I expect to see issues, as hadoop hosts will talk to the KDC via the external address but resolve itself to the internal hostname. I suspect that the Kerberos hostname validation will fail, as the KDC resolves the external IP to the external hostname. Do you have any ideas, how to best handle this situation?
... View more
Labels:
- Labels:
-
Apache Hadoop
-
Kerberos