accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mikewalch <>
Subject [GitHub] accumulo pull request #160: ACCUMULO-4490: Simplify Accumulo scripts and con...
Date Wed, 26 Oct 2016 15:58:23 GMT
Github user mikewalch commented on a diff in the pull request:
    --- Diff: ---
    @@ -26,33 +25,50 @@ source code.  Unpack as follows.
         tar xzf <some dir>/accumulo-X.Y.Z-bin.tar.gz
         cd accumulo-X.Y.Z
    +There are three scripts in the the `bin/` directory that are used to manage Accumulo:
    +1. `accumulo` - Runs Accumulo command-line tools and starts Accumulo processes
    +2. `accumulo-service` - Runs Accumulo processes as services
    +3. `accumulo-cluster` - Manages Accumulo cluster on a single node or several nodes
    +These scripts will be used in the remaining instructions to configure and run Accumulo.
    +Add the following to your `~/.bashrc` if you want to be able to execute these scripts
    +from any directory:
    +    export PATH=/path/to/accumulo-X.Y.Z/bin:$PATH
    +Source your `~/.bashrc` for the changes to take effect and verify:
    +    source ~/.bashrc
    +    which accumulo
    +## Configuring
     Accumulo has some optional native code that improves its performance and
    -stability.  Before configuring Accumulo attempt to build this native code
    +stability.  Before configuring Accumulo, attempt to build this native code
     with the following command.
    -    ./bin/
    -If the command fails, its ok to continue with setup and resolve the issue
    +    accumulo native
    +If the command fails, its OK to continue with setup and resolve the issue later.
    +Run the command below to create some default configuration for Accumulo in `conf/`:
    --- End diff --
    This was fixed

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message