So it seems that the MaxNewSize is simply the default value, refer to "problem 2" in http://bugs.java.com/bugdatabase/view_bug.do?bug_id=6792386 Nothing to worry about. Unfortunately I can't see anything wrong in the histogram, nothing that stands out. :(
On Tuesday, March 11, 2014 8:12:45 PM UTC+1, Corey wrote: > > I have attached the output of the requested commands in the attached > files. > > The only thing that stands out for me is that the MaxNewSize from the > `jmap -heap` command is set to a HUGE number, shall we manipulate that? > > On Tuesday, March 11, 2014 6:18:48 AM UTC-4, Kay Röpke wrote: >> >> Hi Corey! >> >> If that process still running? >> If so, could you send me the output of these commands, please? >> >> jmap -histo:live <pid> >> jmap -heap <pid> >> >> If that doesn't help we would need to find a way to upload the heap dump >> to somewhere. >> Thanks, >> Kay >> >> On Monday, March 10, 2014 2:52:13 PM UTC+1, Corey wrote: >>> >>> After working with Graylog2 0.20.0 for a few weeks we've noticed that >>> the Web Interface is using up more and more of the system's memory as time >>> goes on. We suspect it's the result of a memory leak in the JVM. >>> >>> The attached files contain a thread dump from said JVM. Below is our >>> system information (all services run on the same server): >>> >>> OS: CentOS 6.3 >>> Kernel: 2.6.32-279.22.1.el6.x86_64 >>> Elasticsearch: 0.90.10 >>> MongoDB: 2.4.9 >>> Java: java-1.7.0-openjdk-1.7.0.25 >>> >>> A heap dump that we have taken is too large to be uploaded here, if it's >>> required we will have to find another way to upload it. >>> >> -- You received this message because you are subscribed to the Google Groups "graylog2" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
