accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mikewalch <>
Subject [GitHub] accumulo pull request #235: ACCUMULO-4612 - Simplify Accumulo memory configu...
Date Fri, 24 Mar 2017 16:23:08 GMT
Github user mikewalch commented on a diff in the pull request:
    --- Diff: ---
    @@ -36,62 +36,49 @@ to manage Accumulo:
     These scripts will be used in the remaining instructions to configure and run Accumulo.
     For convenience, consider adding `accumulo-X.Y.Z/bin/` to your shell's path.
    -## Configuring
    +## Configuring Accumulo
    -Accumulo has some optional native code that improves its performance and
    -stability. Before configuring Accumulo, attempt to build this native code
    -with the following command.
    +Accumulo requires running [Zookeeper][3] and [HDFS][4] instances which should be set
    +before configuring Accumulo.
    -    accumulo-util build-native
    +The primary configuration files for Accumulo are `` and `accumulo-site.xml`
    +which are located in the `conf/` directory.
    -If the command fails, its OK to continue with setup and resolve the issue later.
    +Follow the steps below to configure `accumulo-site.xml`:
    -Accumulo is configured by the files `accumulo-site.xml` and `` in the
    -directory. You can either edit these files for your environment or run the command below
which will
    -overwrite them with files configured for your environment.
    +1. Run `accumulo-util build-native` to build native code.  If this command fails, disable
    +   native maps by setting `tserver.memory.maps.native.enabled` to `false`.
    -    accumulo-util create-config
    +2. Set `instance.volumes` to HDFS location where Accumulo will store data. If your namenode
    +   is running at and you want to store data in `/accumulo` in HDFS,
then set
    --- End diff --
    This is now 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