THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Following binaries can be found in the ambari-metrics-assembly/target folder after build is successful.
...
Note: Ambari Metrics needs to be built before Ambari Server
RPM packages
~] cd ambari-metrics ~] mvn clean package -Dbuild-rpm |
Debian packages
Same instruction as above, change the maven target to build-deb
Windows msi
TBU
Command line parameters
| Parameter | Default value | Comment |
|---|---|---|
hbase.tar | http://public-repo-1.hortonworks.com/HDP/centos6/2.x/updates/2.3.0.0/tars/hbase-1.1.1.2.3.0.0-2557.tar.gz | HBase tarball. This is default version for Ambari 2.1.2 |
hbase.folder | hbase-1.1.1.2.3.0.0-2557 | |
hadoop.tar | http://public-repo-1.hortonworks.com/HDP/centos6/2.x/updates/2.3.0.0/tars/hadoop-2.7.1.2.3.0.0-2557.tar.gz | Hadoop tarball, used for native libs. This is default version for Ambari 2.1.2 |
hadoop.folder | hadoop-2.7.1.2.3.0.0-2557 |
Note
After the change introducted by
AMS uses hadoop tars downloaded from Apache by default. Since that version of libhadoop is not built with libsnappy, the following config change in ams-site is needed to make AMS start up correctly.Jira server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key AMBARI-18915
timeline.metrics.hbase.compression.scheme = None