Hadoop is a software platform that lets one easily write and run applications that process vast amounts of data.
This charm provides a simplified connection point for client / workload services which require access to Apache Hadoop. This connection is established via the Apache Bigtop gateway.
The Apache Hadoop software library is a framework that allows for the
distributed processing of large data sets across clusters of computers
using a simple programming model.
This charm facilitates communication between core Apache Bigtop cluster
components and workload charms.
This charm is intended to be deployed via one of the
apache bigtop bundles.
juju quickstart bigtop-processing-mapreduce
This will deploy the Apache Bigtop platform with a workload node
preconfigured to work with the cluster.
You could extend this deployment, for example, to analyze data using Apache Pig.
Simply deploy Pig and attach it to the same plugin:
juju deploy apache-pig pig juju add-relation plugin pig
Status and Smoke Test
Apache Bigtop charms provide extended status reporting to indicate when they
juju status --format=tabular
This is particularly useful when combined with
watch to track the on-going
progress of the deployment:
watch -n 0.5 juju status --format=tabular
The message for each unit will provide information about that unit's state.
Once they all indicate that they are ready, you can perform a "smoke test"
to verify HDFS or YARN services are working as expected. Trigger the
smoke-test action by:
juju action do namenode/0 smoke-test juju action do resourcemanager/0 smoke-test
After a few seconds or so, you can check the results of the smoke test:
juju action status
You will see
status: completed if the smoke test was successful, or
status: failed if it was not. You can get more information on why it failed
juju action fetch <action-id>
- (string) Space separated list of extra deb packages to install.
- (string) List of signing keys for install_sources package sources, per charmhelpers standard format (a yaml list of strings encoded as a string). The keys should be the full ASCII armoured GPG public keys. While GPG key ids are also supported and looked up on a keyserver, operators should be aware that this mechanism is insecure. null can be used if a standard package signing key is used that will already be installed on the machine, and for PPA sources where the package signing key is securely retrieved from Launchpad.
- (string) List of extra apt sources, per charm-helpers standard format (a yaml list of strings encoded as a string). Each source may be either a line that can be added directly to sources.list(5), or in the form ppa:<user>/<ppa-name> for adding Personal Package Archives, or a distribution component to enable.
- (string) The status of service-affecting packages will be set to this value in the dpkg database. Valid values are "install" and "hold".