Accumulo, ZK, Hadoop, and HBase will all have terrible performance if swapping starts happening. The first step is to make sure you allocate an amount of memory appropriate to your hardware. This is covered briefly in the Accumulo manual:
http://accumulo.apache.org/1.5/accumulo_user_manual.html#_edit_conf_accumulo_env_sh The second is to make sure your kernel won't start swapping stuff out early. That's controlled via a setting called vm.swappiness. You can see how to check vm.swappiness and turn it to 0 in the CDH guides, e.g. CDH3: http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH3/CDH3u6/CDH3-Installation-Guide/cdh3ig_topic_9_6.html On Tue, Aug 6, 2013 at 12:35 PM, Mastergeek <[email protected]> wrote: > I did some looking around and I have not found any information on turning > swappiness off. I also did notice that in my log files this line is always > popping up: > > 13/08/06 13:29:58 WARN server.Accumulo: System swappiness setting is > greater > than ten (60) which can cause time-sensitive operations to be delayed. > Accumulo is time sensitive because it needs to maintain distributed lock > agreement. > > Thanks, > Jeff > > > > ----- > > > > -- > View this message in context: > http://apache-accumulo.1065345.n5.nabble.com/MiniAccumuloCluster-connection-timeout-negotiation-tp5049p5057.html > Sent from the Developers mailing list archive at Nabble.com. > -- Sean
