Merge branch '1.7'
Project: http://git-wip-us.apache.org/repos/asf/accumulo/repo Commit: http://git-wip-us.apache.org/repos/asf/accumulo/commit/7f4cb62b Tree: http://git-wip-us.apache.org/repos/asf/accumulo/tree/7f4cb62b Diff: http://git-wip-us.apache.org/repos/asf/accumulo/diff/7f4cb62b Branch: refs/heads/master Commit: 7f4cb62b01595fa3477f7d0917d64ba91ed1ba17 Parents: 7b1e26a 14e88e4 Author: Josh Elser <els...@apache.org> Authored: Mon Dec 28 13:37:25 2015 -0500 Committer: Josh Elser <els...@apache.org> Committed: Mon Dec 28 13:37:50 2015 -0500 ---------------------------------------------------------------------- .../main/asciidoc/chapters/administration.txt | 41 ++++++++++++++++++++ 1 file changed, 41 insertions(+) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/accumulo/blob/7f4cb62b/docs/src/main/asciidoc/chapters/administration.txt ---------------------------------------------------------------------- diff --cc docs/src/main/asciidoc/chapters/administration.txt index 01c5c5c,919ec8f..26ec395 --- a/docs/src/main/asciidoc/chapters/administration.txt +++ b/docs/src/main/asciidoc/chapters/administration.txt @@@ -472,6 -429,46 +472,47 @@@ from the +$ACCUMULO_HOME/conf/slaves+ f ensure that the tabletserver is cleanly stopped and recovery will not need to be performed when the tablets are re-hosted. + ==== Running multiple TabletServers on a single node + + With very powerful nodes, it may be beneficial to run more than one TabletServer on a given + node. This decision should be made carefully and with much deliberation as Accumulo is designed + to be able to scale to using 10's of GB of RAM and 10's of CPU cores. + + To run multiple TabletServers on a single host, it is necessary to create multiple Accumulo configuration + directories. Ensuring that these properties are appropriately set (and remain consistent) are an exercise + for the user. + + Accumulo TabletServers bind certain ports on the host to accommodate remote procedure calls to/from + other nodes. This requires additional configuration values in +accumulo-site.xml+: + + * +tserver.port.client+ + * +replication.receipt.service.port+ + + Normally, setting a value of +0+ for these configuration properties is sufficient. In some + environment, the ports used by Accumulo must be well-known for security reasons and require a + separate copy of the configuration files to use a static port for each TabletServer instance. + + It is also necessary to update the following exported variables in +accumulo-env.sh+. + + * +ACCUMULO_LOG_DIR+ ++* +ACCUMULO_PID_DIR+ + + The values for these properties are left up to the user to define; there are no constraints + other than ensuring that the directory exists and the user running Accumulo has the permission + to read/write into that directory. + + Accumulo's provided scripts for stopping a cluster operate under the assumption that one process + is running per host. As such, starting and stopping multiple TabletServers on one host requires + more effort on the user. It is important to ensure that +ACCUMULO_CONF_DIR+ is correctly + set for the instance of the TabletServer being started. + + $ACCUMULO_CONF_DIR=$ACCUMULO_HOME/conf $ACCUMULO_HOME/bin/accumulo tserver --address <your_server_ip> & + + To stop TabletServers, the normal +stop-all.sh+ will stop all instances of TabletServers across all nodes. + Using the provided +kill+ command by your operation system is an option to stop a single instance on + a single node. +stop-server.sh+ can be used to stop all TabletServers on a single node. + + [[monitoring]] === Monitoring
