[Bug 195861] New: [patch] textproc/elasticsearch set Min JVM heap size = Max JVM heap size

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195861

            Bug ID: 195861
           Summary: [patch] textproc/elasticsearch set Min JVM heap size =
                    Max JVM heap size
           Product: Ports Tree
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: Individual Port(s)
          Assignee: tj at FreeBSD.org
          Reporter: dvl at FreeBSD.org
          Assignee: tj at FreeBSD.org
             Flags: maintainer-feedback?(tj at FreeBSD.org)

Created attachment 150439
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=150439&action=edit
patch rc.d file

In the past, it was standard to set min heap size < max heap size for a JVM.The
current standard approach is to keep them the same.  This avoids the cost of
resizing the JVM heap.

I encountered this issue today when the JVM started spouting repeated errors
(see below).

Conversations in the elasticsearch IRC channel brought the above
recommendation. I implemented it in my /etc/rc.conf file and the problem did
not occur upon restart.


2014-12-10 19:38:26,155][WARN ][index.translog           ] [James Dr. Power]
[logstash-2014.12.10][3] failed to flush shard on translog threshold
org.elasticsearch.index.engine.FlushFailedEngineException:
[logstash-2014.12.10][3] Flush failed
    at
org.elasticsearch.index.engine.internal.InternalEngine.flush(InternalEngine.java:901)
    at
org.elasticsearch.index.shard.service.InternalIndexShard.flush(InternalIndexShard.java:627)
    at
org.elasticsearch.index.translog.TranslogService$TranslogBasedFlush$1.run(TranslogService.java:201)
    at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.lucene.store.AlreadyClosedException: this IndexWriter is
closed
    at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:698)
    at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:712)
    at org.apache.lucene.index.IndexWriter.commit(IndexWriter.java:3063)
    at
org.elasticsearch.index.engine.internal.InternalEngine.flush(InternalEngine.java:891)
    ... 5 more
Caused by: java.lang.OutOfMemoryError: Java heap space

--- Comment #1 from Bugzilla Automation <bugzilla at FreeBSD.org> ---
Auto-assigned to maintainer tj at FreeBSD.org

-- 
You are receiving this mail because:
You are the assignee for the bug.