Which index store are you using? If you are using the fs index, its basic
file handling in Java, no explicit native memory management done in
elasticsearch itself. If you use using memory caching in elasticsearch with
FS, or using memory store module, then by default it allocates native
memory, but it does not relate to files stored on disk, so the fact that the
memory goes away when you delete it make me suspect file caching done by the
os as well...
-shay.banon
On Wed, Jul 7, 2010 at 4:50 PM, Enver enver.cicak@gmail.com wrote:
On Jul 7, 2:23 pm, Clinton Gormley clin...@iannounce.co.uk wrote:
As script generates documents memory usage constantly raises.
Typically, when test finishes, 6GB of memory is used. When I shut down
Elasticsearch process (shutdown, not kill -9... ), memory usage falls
to 4GB. After removing files under elasticsearch/work/
memory usage drops to ~300MB.
It seems that cleanup in not performed correctlyThis sounds like your operating system caching the files in memory for
performance reasons, and is normal.If this memory is required by other processes, the kernel would reduce
the amount of memory used for file caches, but this would also make
future reads/writes to these files less performant.If you're using unix or linux, use the 'top' command to see your memory
usage. If the "Cached" value is high and accounting for memory usage,
then this is the issue (although, it's not an actual issue - it is by
design)maybe i'm way off the mark and have misunderstood your description of
the problemclint
I've seen same behavior when user process does not perform correct
cleanup of shared memory. After process exit memory stays occupied
until shared memory object is deleted.It will be good to have this index store module explained.