Get fresh updates from Hortonworks by email

Once a month, receive latest insights, trends, analytics information and knowledge of Big Data.

Sign up for the Developers Newsletter

Once a month, receive latest insights, trends, analytics information and knowledge of Big Data.

cta

Get Started

cloud

Ready to Get Started?

Download sandbox

How can we help you?

closeClose button
HDP > Hadoop Administration > Hortonworks Sandbox

Hortonworks Sandbox Guide

Sandbox Docs - HDP 2.6.4

cloud Ready to Get Started?

DOWNLOAD SANDBOX

Outline

Release Notes

February 2018

  • Md5 VMware Virtual Appliance – 9ae7becfa0442f66f1dac1ef88477d2f
  • Md5 VirtualBox Virtual Appliance – f2803fdbefab3d2044f8e04957b89090
  • Md5 Docker – (Linux/Mac) b14f4538147851c51b26d9da37ab931c, (Windows) ae377d7dddeb26c89912059a1bf696af
  • HDP Stack and Ambari: The Sandbox uses the following versions of Ambari and HDP stack. Please use the following release note links provided to view Ambari and HDP stack specific information.

Behavior Changes

  • Updated start script to display startup information so as to be more transparent
  • Updated kernel to fix specter and meltdown bugs: 4.4.114-1.el7.elrepo.x86_64

Known Issues

  • Zeppelin interface on port 9995 may require clearing browser cache on some browsers

Limitations

This is a list of common limitations along with their workarounds.

  • RMP-3586 – Due to dependency of the underlying OS and Virtual machine application, the following may occur when suspending the virtual machine:
    • Region Server service for HBase may be stopped when returning back from suspended state. It will need to be restarted.
    • Ambari Metrics may be stopped when returning back from suspended state since it now uses an embedded HBase.
    • Workaround: Avoid having to suspend your virtual machine.

System Information

Operating System and Java versions that the Sandbox has installed.

  • OS Version (docker container)
    • CentOS release 6.9 (Final)
    • Java Version (docker container)
    • openjdk version “1.8.0_161”
    • OpenJDK Runtime Environment (build 1.8.0_161-b14)
    • OpenJDK 64-Bit Server VM (build 25.161-b14, mixed mode)
    • Updated from previous version
  • OS Version (Hosting Virtual Machine)
    • CentOS Linux release 7.2.1511 (Core)

Image File Sizes:

  • VMware – 9.9 GB
  • VirtualBox – 9.7 GB
  • Docker – 12.5 GB

Databases Used

These are a list of databases used within Sandbox along with the corresponding HDP components that use them.

  • Ambari: Postgres
  • Hive Metastore : Mysql
  • Ranger: Mysql
  • Oozie: derby (embedded)

HDP Supported Components Not Installed

These components are offered by the Hortonworks distribution, but not included in the Sandbox.

  • Apache Accumulo
  • Apache Mahout
  • Hue

Newly Added HDP Supported Packages

  • none

HDP Services Started Automatically on Startup

When the virtual machine is booted up, the following services are started. If not specified, assume all are java processes. The users that launch the process are the corresponding names of the component. The processes are listed with their main class.

  • Ambari
    • AmbariServer – org.apache.ambari.server.controller.AmbariServer run as root user
  • Ambari Agent (non java process)
  • Flume
    • Application – org.apache.flume.node.Application
  • HDFS
    • Portmap – org.apache.hadoop.portmap.Portmap
    • NameNode – org.apache.hadoop.hdfs.server.namenode.NameNode
    • DataNode – org.apache.hadoop.hdfs.server.datanode.DataNode
  • Nfs
    • Portmap – Unlike the other processes that are launched by HDFS user, these are run as root user.
    • The nfs process doesn’t show up as a name for jps output
  • HIVE
    • RunJar – webhcat – org.apache.hadoop.util.RunJar Run as hcat user
    • RunJar – metastore – org.apache.hadoop.util.RunJar
    • RunJar – hiveserver2 – org.apache.hadoop.util.RunJar
  • Mapreduce
    • JobHistoryServer – org.apache.hadoop.mapreduce.v2.hs.JobHistoryServer
    • mapred is the user used to launch this process
  • Oozie
    • Bootstrap – org.apache.catalina.startup.Bootstrap
  • Ranger
    • UnixAuthenticationService – org.apache.ranger.authentication.UnixAuthenticationService Run as root user
    • EmbededServer – org.apache.ranger.server.tomcat.EmbeddedServer
  • Spark
    • HistoryServer – org.apache.spark.deploy.history.HistoryServer
  • YARN
    • ApplicationHistoryServer – org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer
    • ResourceManager – org.apache.hadoop.yarn.server.resourcemanager.ResourceManager
    • NodeManager – org.apache.hadoop.yarn.server.nodemanager.NodeManager
  • Zookeeper
    • QuorumPeerMain – org.apache.zookeeper.server.quorum.QuorumPeerMain
  • Zeppelin
    • ZeppelinServer – org.apache.zeppelin.server.ZeppelinServer

HDP Services Not Started Automatically on Startup

Because of the limited resources available in the sandbox virtual machine environment, the following services are in maintenance mode and will not automatically start. To fully use these services, you must allocate more memory to the sandbox virtual machine. If you want these services to automatically start, turn off maintenance mode. The processes are listed with their main class.

  • Ambari Infra
  • Ambari Metrics
  • Atlas
    • Main – org.apache.atlas.Main
  • HDFS
    • SecondaryNameNode – org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode
    • Since on a single node, secondary namenode is not needed, it is not started.
  • Falcon
    • Main – org.apache.falcon.Main
  • HBase
    • HRegionServer – org.apache.hadoop.hbase.regionserver.HRegionServer
    • HMaster – org.apache.hadoop.hbase.master.HMaster
  • Kafka
    • Kafka – kafka.Kafka
  • Knox
    • gateway.jar – /usr/hdp/current/knox-server/bin/gateway.jar
    • ldap.jar – /usr/hdp/current/knox-server/bin/ldap.jar This process is a mini ldap server
  • Spark
    • Livy server run as livy
    • Thrift Server – org.apache.spark.deploy.SparkSubmit run as hive user
  • Spark2
    • Livy server run as livy
    • Thrift server – org.apache.spark.deploy.SparkSubmit run as hive user
  • Storm
    • supervisor – backtype.storm.daemon.supervisor
    • nimbus – backtype.storm.daemon.nimbus
    • logviewer – backtype.storm.daemon.logviewer
    • core – backtype.storm.ui.core
    • drpc – backtype.storm.daemon.drpc

Further Reading