blob: cbea7f02495a1a8f8bac78d57c73ffdb32ef2e4b (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
|
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
## Overview
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.
## Usage
This charm is intended to be deployed via one of the
[apache bigtop bundles](https://jujucharms.com/u/bigdata-dev/#bundles).
For example:
juju deploy hadoop-processing
> Note: With Juju versions < 2.0, you will need to use [juju-deployer][] to
deploy the bundle.
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
[juju-deployer]: https://pypi.python.org/pypi/juju-deployer/
## Status and Smoke Test
Apache Bigtop charms provide extended status reporting to indicate when they
are ready:
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
via:
juju action fetch <action-id>
## Contact Information
- <bigdata@lists.ubuntu.com>
## Resources
- [Apache Bigtop](http://bigtop.apache.org/) home page
- [Apache Bigtop issue tracking](http://bigtop.apache.org/issue-tracking.html)
- [Apache Bigtop mailing lists](http://bigtop.apache.org/mail-lists.html)
- [Apache Bigtop charms](https://jujucharms.com/q/apache/bigtop)
|
