cjmctague closed pull request #194: update README to cover clean up. URL: https://github.com/apache/fluo-uno/pull/194
This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (from a fork), the diff is supplied below (as it won't show otherwise due to GitHub magic): diff --git a/README.md b/README.md index 6888056..0315142 100644 --- a/README.md +++ b/README.md @@ -54,6 +54,11 @@ and password `secret` (set in the `uno.conf` file). Therefore, the shell can be accumulo shell -u root -p secret ``` +When you're all done testing out Accumulo you can clean up: +``` +./bin/uno wipe +``` + For a more complete understanding of Uno, please continue reading. ## Installation @@ -113,7 +118,7 @@ upgrade components and need to download/build the latest version. ## Setup command -The `setup` command will install the downloaded tarballs to the directory set by `$INSTALL` in your +The `uno setup` command will install the downloaded tarballs to the directory set by `$INSTALL` in your `uno.conf` and run you local development cluster. The command can be run in several different ways: 1. Sets up Apache Accumulo and its dependencies of Hadoop, ZooKeeper. This starts all processes and @@ -161,6 +166,13 @@ to administer Fluo: If you run some tests and then want a fresh cluster, run the `setup` command again which will kill all running processes, clear any data and logs, and restart your cluster. +## Wipe command + +The `uno wipe` command will kill all running processes for your local development cluster and clear +all the data and logs. It does *not* delete the binary tarballs downloaded by the `fetch` command +so you can use `setup` directly again in the future. If you need to reclaim the space used by +the binary tarballs you'll have to manually delete them. + ## Running Apache Fluo applications Before running an Apache Fluo application, it is recommended that you configure your shell using ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
