- Release Notes
- System Information
- Services Started Automatically
- Services In Maintenance Mode
- Further Reading
- The VirtualBox and VMWare releases of the HDF sandox had their OS-level packages updated, including a version update of Docker from 17.09 to 17.12.
- A patch was applied to the released VMs which updated them to the 4.14.14-1 kernel to address the Meltdown/Spectre vulnerability.
- The VirtualBox and VMWare releases were reduced to a total size of about 10.4 GB. As a result, a loading splash page will show up on first boot while the sandbox is decompressed and set up.
- Minor splash page typo fixes.
- The Sandbox uses the following versions of Ambari, HDF and HDP. Please use the following release note links provided to view their respective release notes.
Operating System and Java versions that the Sandbox has installed.
- CentOS release 7.4.1708
- Kernel: 4.14.14-1
- Java: OpenJDK version 1.8.0_131
Image File Sizes:
- Docker – 10 GB compressed, 13.9 GB uncompressed
- VMware – 10.4 GB
- Virtualbox – 10.4 GB
- Docker release – MD5:c5023721b73693e9cbca1df7e2aeaba2
- VMware release – MD5:be4aaf555cdb1aac08e5f42e90874338
- Virtualbox release – MD5:fca5d03bdc70070cf5f7ccd42c9a1496
These are a list of databases used within the HDF Sandbox along with the HDF components that use them.
- PostgreSQL: Ambari
- MySQL: Registry, Streaming Analytics Manager, Druid, Superset
Services Started Automatically
When the sandbox is started, the following services are also started by default. Unless specified, assume all are java processes and the user that launches the process is named the same as the component (i.e. The Storm process is run by the user “storm”).
- Ambari Server (run as root user)
- Ambari Agent (non-java)
- Streaming Analytics Manager (run as streamline user)
Services In Maintenance Mode
Due to limited resources avaialble in the sandbox’s virtual 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’s virtual machine or turn off existing services. If you want these services to automatically start, turn off maintenance mode from within the Ambari dashboard.