> I did heap dump + heap histogram before killing the jvm today and the
only really suspicious thing was the top line in the histogram:
class [B,
81883 instances,
3,974,092,842 bytes
> Most of the instances (actually all of around a hundred of them I
checked with jhat) look almost the same in term
Today I've managed to get the following from a "dead" server:
- gc log since start till the death of the service
- jutil -gc -t 1000 output since start till the end
- thread stack dump before killing the server
- heap histogram before killing the server
- heap dump
On Fri, Dec 24, 2010 at 11:36
More details, please. You tried all of the different GC
implementations? Is there enough memory assign to the JVM to run
comfortably but no much more? (The OS uses spare memory as disk
buffers a lot better than Java does.)
How many threads are there? Distributed search uses two searches, both
para
Hello guys,
We at scribd.com have recently deployed our new search cluster based
on Dec 1st, 2010 branch_3x solr code and we're very happy about the
new features in brings.
Though looks like we have a weird problem here: once a day our servers
handling sharded search queries (frontend servers that
