@Raj Kumar The pictures are not working for me, so I am answering based on an assumption that we see commonly. There are two layers on the HDP Sandbox (Docker and the VM). When using an SSH client, be sure to double check that you are using port 2222 for the Sandbox, and port 2122 if you need to access the Docker side (normally not needed unless you are adding ports). ... View more

@Marcy Using the Hive CLI, the connection is direct to the Hive Metastore, and relies on Storage-based Authorization. To take advantage of the Ranger-based central security, Hortonworks recommends using Beeline (instead of the Hive CLI) as it will go through HiveServer2 and the Ranger-based policies will apply. In fact, in production environments, it is often suggested to have administrators disable the hive CLI and force users to issue CLI-based interactions through Beeline. Here are some relevant links that you may find useful. As always, if you find this post useful, don't forget to upvote and/or accept the answer. http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.5.3/bk_data-access/content/beeline-vs-hive-cli.html https://community.hortonworks.com/articles/10367/apache-ranger-and-hive-column-level-security.html https://community.hortonworks.com/questions/10760/how-to-disable-hive-shell-for-all-users.html ... View more

@Eric England The goal of LogSearch was indeed for cluster components, and not third party logs. Hortonworks does provide a solution that could work for third party logs with HDP Search (Solr/Banana) on the HDP cluster that you may want to look at. Here are some links that may be useful: https://hortonworks.com/apache/solr/ http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.5.3/bk_solr-search-installation/content/ch_hdp-search.html As always, if you find this post useful, don't forgot to upvote and/or accept the answer. ... View more

hi @Vinay R HDFS Snapshots are point in time copies of the filesystem and taken either on a dir or the entire FS, depending on the administrator's preferences/policies. When you take a snapshot using the -createSnapshot command on a dir, a ".snapshot" dir will be created (usually with a timestamp appended by default but can be something else if you wish). The blocks of data within that HDFS dir are then protected (meaning the dir becomes read-only), and any subsequent delete commands will alter the metadata stored in the namenode only. Since the blocks are preserved, one can use the snapshots to restore the data as well. There is no time-limit on snapshots, so you can recover blocks from a few weeks back in your example if someone took a snapshot of them before any delete commands. There are however upper limits on the number of simultaneous snapshots that can be taken (though it is large at 65536). When snapshots are being used, care should also be taken to ensure snapshots are also being cleaned up to avoid clogging up the system. Here are a couple of useful links on Snapshots that you may want to review: http://hortonworks.com/hadoop-tutorial/using-hdfs-snapshots-protect-important-enterprise-datasets/ https://hadoop.apache.org/docs/r2.7.2/hadoop-project-dist/hadoop-hdfs/HdfsSnapshots.html As always, if you find this post useful, don't forgot to upvote and/or accept the answer. ... View more

@Murray S The sandbox-version command should definitely work if you are SSHd into the correct environment using port 2222 and logged in as root. I think your command to start Ambari is invalid though, I believe it should be as follows: service ambari-server [status|start|stop|restart] The other way in is to use the web SSH tool: http://127.0.0.1:4200/ I find this a bit more convenient than using the direct access on VirtualBox. If you can login there with root, you can try changing the Ambari admin password again: ambari-admin-password-reset Once you change the Ambari admin password, try logging in as the admin via: http://127.0.0.1:8080 Otherwise you always have the option of deleting the Virtual Box VM and re-importing the appliance to start over again ... View more