The Apache Mahout project's goal is to build an environment for quickly creating scalable, performant machine learning applications.
This charm provides version 0.13.0 of the Mahout application from Apache Bigtop.
The Apache Mahout project's goal is to build an environment for quickly
creating scalable, performant machine learning applications. Learn more at
This charm deploys version 0.13.0 of the Mahout component from
This charm requires Juju 2.0 or greater. If Juju is not yet set up, please
follow the getting-started instructions prior to deploying this charm.
This charm is intended to be used with one of the apache bigtop bundles.
juju deploy hadoop-processing
This will deploy an Apache Bigtop Hadoop cluster. More information about this
deployment can be found in the bundle readme.
Now add Mahout and relate it to the cluster endpoint:
juju deploy mahout
juju add-relation mahout client
Charms can be deployed in environments with limited network access. To deploy
in this environment, configure a Juju model with appropriate proxy and/or
mirror options. See Configuring Models for more information.
Apache Bigtop charms provide extended status reporting to indicate when they
This is particularly useful when combined with watch to track the on-going
progress of the deployment:
watch -n 2 juju status
The message column will provide information about a given unit's state.
This charm is ready for use once the status message indicates that it is
This charm provides a smoke-test action that can be used to verify the
application is functioning as expected. Run the action as follows:
juju run-action mahout/0 smoke-test
Watch the progress of the smoke test actions with:
watch -n 2 juju show-action-status
Eventually, the action should settle to status: completed. If it
reports status: failed, the application is not working as expected. Get
more information about a specific smoke test with:
juju show-action-output <action-id>
Apache Bigtop tracks issues using JIRA (Apache account required). File an
issue for this charm at:
Ensure Bigtop is selected as the project. Typically, charm issues are filed
in the deployment component with the latest stable release selected as the
affected version. Any uncertain fields may be left blank.