Merge lp://staging/~james-page/charms/precise/hadoop/storage-options into lp://staging/~charmers/charms/precise/hadoop/trunk
Proposed by
James Page
| Status: | Merged |
|---|---|
| Merged at revision: | 27 |
| Proposed branch: | lp://staging/~james-page/charms/precise/hadoop/storage-options |
| Merge into: | lp://staging/~charmers/charms/precise/hadoop/trunk |
| Diff against target: |
80 lines (+27/-3) 3 files modified
config.yaml (+10/-0) hooks/hadoop-common (+16/-2) revision (+1/-1) |
| To merge this branch: | bzr merge lp://staging/~james-page/charms/precise/hadoop/storage-options |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Marc Cluet (community) | Approve | ||
|
Review via email:
|
|||
Description of the change
This branch adds a storage option which allows all hadoop data to be stored
in a filesystem outside of root.
This supports using /mnt in ec2 (mainly)
To post a comment you must log in.
Revision history for this message
| Clint Byrum (clint-fewbar) wrote | # |
Revision history for this message
| James Page (james-page) wrote | # |
Preview Diff
[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
Hi James. My only question would be whether or not we can just make it so the data is inaccessible if the value is changed, and can be made accessible again if it is changed back. "Lose all your data" sounds pretty scary.