Member since
09-21-2016
57
Posts
0
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
5342 | 05-17-2017 03:42 AM |
10-21-2025
04:35 PM
We would need to understand first if the issue is on the CM-agent or on the Nifi-registry. Simply describing if the nifi-registry did not start at all or did start but then failed would help in knowing if the issue is with CM-agent or nifi-registry itself.
... View more
05-17-2017
03:42 AM
dfs.namenode.datanode.registration.ip-hostname-check If true (the default), then the namenode requires that a connecting datanode's address must be resolved to a hostname. If necessary, a reverse DNS lookup is performed. All attempts to register a datanode from an unresolvable address are rejected. It is recommended that this setting be left on to prevent accidental registration of datanodes listed by hostname in the excludes file during a DNS outage. Only set this to false in environments where there is no infrastructure to support reverse DNS lookup.
... View more
05-17-2017
03:24 AM
You can execute the following tests bellow, usually the sanbox hdfs is not set to listen to localhost, but to sandbox.hortonworks.com; hdfs$ hdfs dfs -ls hdfs://sandbox.hortonworks.com/tmp You can try with localhost and should fail with the same Error: hdfs$ hdfs dfs -ls hdfs://localhost/tmp To check, just go to ambari:services:hdfs:configs:Advance and filter for port number 8020;
... View more