You can adjust the value of 'tserver.memory.maps.max' in
accumulo-site.xml. This will require a restart of the tabletservers.
I'm a little confused as to why you're concerned about having KVs in
memory though. If you're not running out of memory, this is typically a
good thing to have data hanging around in memory for a bit.
On 10/28/13, 5:19 PM, Terry P. wrote:
Greetings all,
For a growing table that currently from zero to 70 million entries this
weekend, I'm seeing 4.4 million entries still in memory, though the
client programs are supposed to be flushing their entries.
Is there a server-side setting to help reduce the number of entries that
are in memory (not yet flushed to disk)? Our system has fairly light
performance requirements, so I'm okay if a tweak may result in reduced
ingest performance.
Thanks in advance,
Terry
