Member since
01-19-2017
3682
Posts
633
Kudos Received
373
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 1732 | 06-04-2025 11:36 PM | |
| 2166 | 03-23-2025 05:23 AM | |
| 1035 | 03-17-2025 10:18 AM | |
| 3966 | 03-05-2025 01:34 PM | |
| 2710 | 03-03-2025 01:09 PM |
02-07-2019
10:17 AM
@christophe VALMIR Any updates?
... View more
02-07-2019
08:05 AM
1 Kudo
@ram sriram The below command sets your replication factor to 1 for all new files you will create, with a potential data loss unless you are running HDP 3.x which has a new HDFS algorithm EC erasure coding $ hdfs dfs -setrep -w 1 -R / As responded above the changes only affect new files you will create. After changing the replication factor you won't see any hdfs size changes until the trash time interval which was set on 360 minutes configured by the hdfs trash interval has been reached fs.trash.interval Once the NameNode metadata has been updated, it is the DataNodes which would actually do the operation. There could be some delay, but space is definitely reclaimed. HTH
... View more
02-06-2019
01:03 PM
@Chris Jenkins My pleasure I made your day and welcome to Big data space, having to go all through all this will make you better technically you've now seen the different facets to resolving a problem. Happy Hadooping !
... View more
02-05-2019
08:11 PM
@christophe VALMIR After running the --mpack you usually need to restart Ambari server. In the document, you quoted at which step are you stuck?
... View more
02-05-2019
04:48 PM
@Al Kirmer Unfortunately its a hard and fast rule when it comes to paid support. HWX won't take responsibility or guarantee good functionality of your cluster or it's components. HWX does extensive testing before adding a third-party software/tool on its support list. I am not an HW employee but I bet you will get the same response HWX could be in the process of certifying those versions but after the merge with Cloudera I am pretty sure there won't be any major releases until the new Cloudera Data Platform (CDP) new name for the next product is out sometime in or after 2020 currently there are teams involved in the integration and choice of the best products from both worlds HWX & CDH HTH
... View more
02-05-2019
09:20 AM
@Chris Jenkins Yes for sure I understood you were running the wget from the guest, that proves that Ambari is responding on port 8080. FW Firewall (FW) there could be a firewall running on your host. Have you tried the port forwarding see attache screenshots! If you can access 8080 from the guest then for sure the issue is the port forwarding between your guest and host
... View more
02-04-2019
10:05 PM
@Chris Jenkins We are almost there 🙂 By now your ambari should have been accessible from localhost: 8080, as you can run a WGET successfully then you have a DNS,FW or do you have any popup blocker, can you try Chrome incognito? Can you try the Putty Local Port Forwarding Please revert
... View more
02-04-2019
03:30 PM
@Chris Jenkins I didn't see you run the below command as root, this resets the Ambari admin password which is shipped with the image and starts it at port 8080. # ambari-admin-password-reset Please could you try that and let me know
... View more
02-04-2019
08:30 AM
@Chris Jenkins I just downloaded and successfully deployed the sandbox please see the short document attached and see if there is something you did wrong. Please let me know
... View more
02-03-2019
01:52 PM
@Shraddha Singh This is database connection issue it seems you haven't set the database for rangerkms !! If you other databases are running on Mysql or MariaDB do the following are the root user if not use the appropriate syntax. Usually the all the databases are co-hosted on the same node for hive, oozie, Ambari etc mysql -uroot -p{root_password}
create database rangerkms;
create user 'rangerkms'@'localhost' identified by '{rangerkms_password}';
grant all privileges on rangerkms.* to 'rangerkms'@'localhost';
grant all privileges on rangerkms.* to 'rangerkms'@'%';
grant all privileges on rangerkms.* to 'rangerkms'@'{DB_HOST}' identified by '{rangerkms_password}';
grant all privileges on rangerkms.* to 'rangerkms'@'{DB_HOST}' with grant option;
grant all privileges on rangerkms.* to 'rangerkms'@'%' with grant option;
flush privileges;
quit; After the above statements have run successfully use the above user/password to reconfigure your rangerkms it should start up HTH
... View more