Member since
03-14-2016
4721
Posts
1111
Kudos Received
874
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 2714 | 04-27-2020 03:48 AM | |
| 5273 | 04-26-2020 06:18 PM | |
| 4443 | 04-26-2020 06:05 PM | |
| 3566 | 04-13-2020 08:53 PM | |
| 5375 | 03-31-2020 02:10 AM |
06-01-2017
09:41 AM
@white wartih Can you pelase share the complete stackTrace of the failure from the ambari-server.log?
... View more
06-01-2017
08:59 AM
@nshelke
Perfect solution, thanks.
... View more
06-01-2017
07:27 AM
1 Kudo
@arjun more A workaround that i think at this point may be: 1) Stop All region servers
2) Login to Master then perform the removal of "/hbase-unsecure" (i assume your cluster is non kerberized) hbase zkcli
rmr /hbase-unsecure
3). Restart HBase . NOTE: You should always think twice before running "rmr /hbase-unsecure"
... View more
06-01-2017
03:59 AM
1 Kudo
@John Cleveland
Good to know that your issue is resolved. Few details: hadoop.proxyuser.<USER>.hosts From File View perspective: Here we need to replace the <USER> with the username who is actually running the Ambari Server (Or Standalone Ambari FileView Server) . So if you are running ambari server as "root" user then you will need to set the property for "root" user as "hadoop.proxyuser.root.groups". The Value of this property can be a comma separated list of addresses where you are running the ambari server (OR Standalone View Ambari Server for hosting the View) . Because View Server will actually send requests to Hadoop. So hadoop need to allow access from the host where the FileView is running. Setting * means you can use the FileView (Standalone Ambari View Server) which is installed to any host. (In a kerberized environment we need to replace the <USER> with the ambari server kerberos principal name). From Generic Hadoop Perspective: In general, By Using proxy user using properties "hadoop.proxyuser.$superuser.hosts" along with either or both of "hadoop.proxyuser.$superuser.groups" and "hadoop.proxyuser.$superuser.users".
By specifying as below in core-site.xml, the superuser named super can connect only from host1 and host2 to impersonate a user belonging to group1 and group2.
Following document explains it with examples: https://hadoop.apache.org/docs/r2.7.3/hadoop-project-dist/hadoop-common/Superusers.html
... View more
06-01-2017
03:49 AM
@Robin Dong If your instance is in a VPC and you assign it an Elastic IP address, it receives an IPv4 DNS hostname if DNS hostnames are enabled. For more information, see Using DNS with Your VPC in the Amazon VPC User Guide. [1] & [2] Note: Instances that access other instances through their public NAT IP address are charged for regional or Internet data transfer, depending on whether the instances are in the same region.
[1] Reference Doc: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html [2] http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-dns.html AWS Forums (reporting such behaviour): https://forums.aws.amazon.com/thread.jspa?threadID=122633 .
... View more
06-01-2017
02:48 AM
@Robin Dong Sometimes this can happen in a scenario where as soon as the instances are shutdown and restarted back, the IP
addresses and hostnames change, which means the cluster doesn’t know
where to find its various services. .
... View more
06-01-2017
12:49 AM
1 Kudo
@John Cleveland Looks like you have not added the mentioned IP Address properly inside the property: hadoop.proxyuser.root.hosts
If ambari-server daemon is running as root, you set up a proxy user for root in core-site by adding and changing properties in HDFS > Configs > Custom core-site:
hadoop.proxyuser.root.groups=*
hadoop.proxyuser.root.hosts=*
OR
hadoop.proxyuser.root.hosts=192.168.70.104
Here You can also define a comma separate IP Address list so that File View access will be allowed from the mentioned address to avoid this error: Unauthorized connection for super-user: root from IP 192.168.70.104 .
... View more
05-31-2017
12:11 PM
@Robin Dong
For understanding and walk through of SmartSense you can refer to the Hortonworks Article: https://community.hortonworks.com/articles/34201/how-to-inspect-smartsense-bundle-contents.html And https://www.slideshare.net/ChrisNauroth/keep-your-hadoop-cluster-at-its-best-v4
... View more
05-31-2017
06:22 AM
@Robin Dong Which version of ambari are you using ? If you are using Ambari version 2.4.x, and want to use SmartSense 1.4.x, you must
first download and install it (Downloading and Installing SmartSense Binary). Please see: https://docs.hortonworks.com/HDPDocuments/SS1/SmartSense-1.4.0/bk_installation/content/ambari_install.html From Ambari 2.5 this behaviour is changed : https://docs.hortonworks.com/HDPDocuments/Ambari-2.5.0.3/bk_ambari-release-notes/content/ambari_relnotes-2.5.0.3-behavioral-changes.html .
... View more
05-30-2017
04:39 PM
@Ramon Wartala
What principals do you see when you run the following command using "kadmin.local" on the KDC ? # kadmin.local -q "listprincs" | grep zookeeper .
... View more