[CASSANDRA-13096] Snapshots slow down jmx scraping

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Not A Problem
• Component/s: Observability/Metrics
• Severity: Normal
• Assignee: Unassigned Assign to me
• Reporter: Maxime Fouilleul
• Created: 04/Jan/17 17:04
• Updated: 28/Apr/22 19:57
• Resolved: 14/Dec/20 16:02

Description

Hello,

We are scraping the jmx metrics through a prometheus exporter and we noticed that some nodes became really long to answer (more than 20 seconds). After some investigations we do not find any hardware problem or overload issues on there "slow" nodes. It happens on different clusters, some with only few giga bytes of dataset and it does not seams to be related to a specific version neither as it happens on 2.1, 2.2 and 3.0 nodes.

After some unsuccessful actions, one of our ideas was to clean the snapshots staying on one problematic node:

nodetool clearsnapshot

And the magic happens... as you can see in the attached diagrams, the second we cleared the snapshots, the CPU activity dropped immediatly and the duration to scrape the jmx metrics goes from +20 secs to instantaneous...

Can you enlighten us on this issue? Once again, it appears on our three 2.1, 2.2 and 3.0 versions, on different volumetry and it is not systematically linked to the snapshots as we have some nodes with the same snapshots volume which are going pretty well.

Issue Links

• relates to: CASSANDRA-16843 List snapshots of dropped tables