Re:The Elastic Stack: Future of ELK Platform
by gibrown on Thursday February 18, 2016 @05:39AM
(#11124873)
230MB of Heap is very small for most ES usages, and is likely the reason for you needing to restart it often. I run some very large clusters and even with older versions of ES have seen them run billions of indexing and query operations without problems for 4-6 months without any restarts.
[ Parent
| on HN ]
Re:The Elastic Stack: Future of ELK Platform
by dozzie on Thursday February 18, 2016 @06:12AM
(#11125008)
> 230MB of Heap is very small for most ES usages
230MB RSS, and this is not "ES usage", it's just after starting it with no data whatsoever. I've seen databases which use less memory than that when working.
> I run some very large clusters [...] without problems for 4-6 months without any restarts.
Well, good for you. Being a sysadmin, I understand very well that my ES server may be a specimen combining bad kernel compilation, broken JVM version, unstable ES release, and ground water emanating bad energy, so I don't complain much. Still, I would be very, very happy to see any alternative for storing JSONified logs.
Re:The Elastic Stack: Future of ELK Platform
by packetized on Thursday February 18, 2016 @10:21AM
(#11126348)
Despite what they recommend, I'd move to G1GC over CMS. Did wonders for our stability. This is on ES2.1.0 & OpenJDK 1.8.0-u80, IIRC.