Title: JVM Garbage Collection logs, you do not want to ignore them!

Type: Ignite

Tags: JVM GC debugging


Status: accepted

Developing your application in Java or in one of the other JVM languages such as Scala, Clojure, Groovy or JRuby?
Basing your infrastructure on a JVM based third party service such as Spark,Cassandra,Storm, Kafka, Elastic Search, Finagle etc?
If the answer to one of the questions is yes you should configure and monitor the JVM Garbage collection logs. Failing to do so may expose you to scalability and latency issues that won't even make sense unless you are aware of the behavior (or misbehavior) of your garbage collector.
In this ignite talk we will briefly learn how to configure the logs and how to interpret them.