You can limit the off-heap space used by setting ES_DIRECT_SIZE.
--
Ivan
On Tue, Apr 8, 2014 at 1:31 PM, Yitzhak Kesselman ikessel...@gmail.comwrote:
Hi,
I have experienced same behavior when I have tried to load large amount of
data... If you clear the file system cache
Hi,
I have experienced same behavior when I have tried to load large amount of
data... If you clear the file system cache
(herehttp://www.delphitools.info/2013/11/29/flush-windows-file-cache/is a
link to a tool), the memory drops to the defined heap size.
However this is still looks as a wrong
As a follow-up, when the server is nearing maximum memory, the memory use
stops increasing. This would indeed support Zachary's caching theory,
although I'm still confused as to why it shows up as 'in use' memory rather
than 'cached' memory. In any case, it does not block me right now. It's
How much heap, what java version, how big are your indexes?
Regards,
Mark Walkom
Infrastructure Engineer
Campaign Monitor
email: ma...@campaignmonitor.com
web: www.campaignmonitor.com
On 14 March 2014 11:11, Jos Kraaijeveld m...@kaidence.org wrote:
I forgot to mention, I'm running
I believe you are just witnessing the OS caching files in memory. Lucene
(and therefore by extension Elasticsearch) uses a large number of files to
represent segments. TTL + updates will cause even higher file turnover
than usual.
The OS manages all of this caching and will reclaim it for
@Mark:
The heap is set to 2GB, using mlockall. The problem occurs with both
OpenJDK7 and OracleJDK7, both the latest versions. I have one index, which
is very small:
index:
{
primary_size_in_bytes: 37710681
size_in_bytes: 37710681
}
@Zachary Our systems are set up to alert when memory is about
Cool, curious to see what happens. As an aside, I would recommend
downgrading to Java 1.7.0_u25. There are known bugs in the most recent
Oracle JVM versions which have not been resolved yet. u25 is the most
recent safe version. I don't think that's your problem, but it's a good
general
Also, are there other processes running which may be causing the problem?
Does the behavior only happen when ES is running?
On Thursday, March 13, 2014 8:31:18 PM UTC-4, Zachary Tong wrote:
Cool, curious to see what happens. As an aside, I would recommend
downgrading to Java 1.7.0_u25.
