Clinton,
excuse my french, but you are a fucking genius 
Changing the store type to mmapfs radically changed the memory buildup.
It's still a bit soon to say if it really fixed the problem, but We have a
test that would consistently make the problem appear in about 5h, and now
it's been running for more than 24h and still ok.
I dont know if other people experienced that before, but maybe mmap
should be the default, or at least, recommended setting for 64bit systems?
thanks again
leo
http://twitter.com/leonardomenezes
On Thu, Feb 21, 2013 at 4:17 PM, Clinton Gormley clint@traveljury.comwrote:
On Thu, 2013-02-21 at 16:08 +0100, Leonardo Menezes wrote:
We tried 30GB but we ran into the same problem, that's why we actually
incremented to 40gb. About the mmapfs, isnt nio the recommended one?
Any reason to believe nio might have a problem?You're on 64 bit?
If so, give this a read:
The Generics Policeman Blog: Use Lucene’s MMapDirectory on 64bit platforms, please!but either way, you don't want your heap above 30GB. Rather leave the
rest of the RAM for your file system caches.clint
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.