Here's the metrics you want. Depends on what GC you're using as Dimo said
above.
*1) If you're using CMS - Collection time / Collection count (Avg time per
collection)*
*ParNew*
(java.lang.type=GarbageCollector.name=ParNew.CollectionTime /
java.lang.type=GarbageCollector.name=ParNew.CollectionCount)
*CMS*
(java.lang.type=GarbageCollector.name=ConcurrentMarkSweep.CollectionTime /
java.lang.type=GarbageCollector.name=ConcurrentMarkSweep.CollectionCount)
*2) If you're using G1GC - Collection time / Collection count (Avg time per
collection)*
*Young Gen*
(java.lang.type=GarbageCollector.name=G1 Young Generation.CollectionTime /
java.lang.type=GarbageCollector.name=G1 Young Generation.CollectionCount)
*Old Gen*
(java.lang.type=GarbageCollector.name=G1 Old Generation.CollectionTime /
java.lang.type=GarbageCollector.name=G1 Old Generation.CollectionCount)
On Thu, Jun 27, 2019 at 11:56 AM Dimo Velev <dimo.ve...@gmail.com> wrote:
> That is s standard jvm metric. Connect to your cassandra node with a JMX
> browser (jconsole, jmc, ...) and browse the metrics. Depending on the
> garbage collector you use, they will be different but are there
>
> On Thu, 27 Jun 2019, 13:47 Ahmed Eljami, <ahmed.elj...@gmail.com> wrote:
>
>> Hi,
>>
>> I want to know if it's possible to get information about GC pause
>> duration (Stop the world) via JMX.
>>
>> Today, we get this information from gc.log with the JVM option
>> XX:+PrintGCApplicationStoppedTime{color}
>>
>> Total time for which application threads were stopped: 0.0001273 seconds,
>> Stopping threads took: 0.0000196 seconds
>>
>> A python script is deployed on every node to parsing the gc.log
>>
>>
>> and it works quite well, but on a Kubernetes environnement, we will have
>> to create a sidecar inside a pod what we try to avoid.
>>
>> Thanks
>>
>
--
www.vorstella.com
408 691 8402
