Github user keith-turner commented on a diff in the pull request:

    https://github.com/apache/accumulo/pull/110#discussion_r66085575
  
    --- Diff: docs/src/main/asciidoc/chapters/administration.txt ---
    @@ -479,40 +479,22 @@ With very powerful nodes, it may be beneficial to run 
more than one TabletServer
     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.
    +To run multiple TabletServers on a single host you will need to change the 
+NUM_TSERVERS+ property
    +in the accumulo-env.sh file from 1 to the number of TabletServers that you 
want to run. On NUMA
    +hardware, with numactl installed, the TabletServer will interleave its 
memory allocations across
    +the NUMA nodes and the processes will be scheduled on all the NUMA cores 
without restriction. To
    +change this behavior you can uncomment the +TSERVER_NUMA_OPTIONS+ example 
in accumulo-env.sh and
    +set the numactl options for each TabletServer.
     
     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+:
    +other nodes. Running more than one TabletServer on a host requires that 
you set the following
    +properties to zero in +accumulo-site.xml+:
    --- End diff --
    
    You could replace the following line with the xml that needs to be pasted 
into accumulo-site.xml.  


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to