Why am I getting GC Allocation Failures in Cassandra logs?

Question

question

davi_prosesor2008_192135 asked · Jun 18 at 08:33 AM

Why am I getting GC Allocation Failures in Cassandra logs?

now i get gc error in cassandra, what should i do when i get this error?

2020-06-18T14:09:23.306+0700: 76241.675: [GC (Allocation Failure) 

2020- 06-18T14:09:23.306+0700: 76241.675: [ParNew Desired survivor size 83886080 bytes, new threshold 1 (max 1) - age 1: 102072 bytes, 102072 total : 1311093K->121K(1474560K), 0.0063021 secs] 3451962K->2141004K(8028160K ), 0.0065244 secs] [Times: user=0.07 sys=0.00, real=0.01 secs] Heap after GC invocations=3583 (full 6): par new generation total 1474560K, used 121K [0x00000005cc000000, 0x0000000630000000, 0x0000000630000000) eden space 1310720K, 0% used [0x00000005cc000000, 0x00000005cc000000, 0x000000061c000000) from space 163840K, 0% used [0x0000000626000000, 0x000000062601e470, 0x0000000630000000) to space 163840K, 0% used [0x000000061c000000, 0x000000061c000000, 0x0000000626000000) concurrent mark-sweep generation total 6553600K, used 2140883K [0x0000000630000000, 0x00000007c0000000, 0x00000007c0000000) Metaspace used 47256K, capacity 48753K, committed 49120K, reserved 1091584K class space used 5706K, capacity 6017K, committed 6112K, reserved 1048576K } 

2020-06-18T14:09:23.313+0700: 76241.682: Total time for which application threads were stopped: 0.0074619 seconds, Stopping threads took: 0.0002640 seconds {Heap before GC invocations=3583 (full 6): par new generation total 1474560K, used 1310841K [0x00000005cc000000, 0x0000000630000000, 0x0000000630000000) eden space 1310720K, 100% used [0x00000005cc000000, 0x000000061c000000, 0x000000061c000000) from space 163840K, 0% used [0x0000000626000000, 0x000000062601e470, 0x0000000630000000) to space 163840K, 0% used [0x000000061c000000, 0x000000061c000000, 0x0000000626000000) concurrent mark-sweep generation total 6553600K, used 2140883K [0x0000000630000000, 0x00000007c0000000, 0x00000007c0000000) Metaspace used 47256K, capacity 48753K, committed 49120K, reserved 1091584K class space used 5706K, capacity 6017K, committed 6112K, reserved 1048576K 2020-06-18T14:10:12.454+0700: 76290.823: [GC (Allocation Failure) 

2020-06-18T14:10:12.454+0700: 76290.823: [ParNew Desired survivor size 83886080 bytes, new threshold 1 (max 1) - age 1: 12515672 bytes, 12515672 total : 1310841K->12277K(1474560K), 0.0072744 secs] 3451724K->2153236K(8028160K), 0.0075026 secs] [Times: user=0.08 sys=0.00, real=0.01 secs]

cassandra garbage collection

1

10 |1000 characters needed characters left characters exceeded

Attachments: Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

bettina.swynnerton ♦♦ · Jun 18 at 09:39 AM

Hi,

would you confirm your cassandra version and paste the messages from the system.log around this time ( 2020-06-18T14:09:23.306+0700 ), so we get a better understanding of how this presents as an error? The pasted logs appear to come from the gc logs, and there is evidence of a short gc pause:

Total time for which application threads were stopped: 0.0074619 seconds

Allocation failures trigger minor garbage collections and are a normal part of GC, not necessarily an error.

0 · ·

Answer 1 · 2020-06-24T09:17:16Z

bettina.swynnerton answered · Jun 24 at 09:17 AM

Without further context and error description, we won't be able to help here unfortunately.

The pasted logs appear to come from the gc logs, there is evidence of a short gc pause, but this does not indicate any errors or problems.

Allocation failures trigger minor garbage collections and are a normal part of GC.

If you see any errors, please provide the error traces from the cassandra system.log as a start.

Thanks!

Share

10 |1000 characters needed characters left characters exceeded

Attachments: Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

PLANNED MAINTENANCE

question