◆ Apache Cassandra

Diagnose high CPU usage issues

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskProvide the CPU utilization for all Cassandra nodes in the analytics cluster over the last…+
Provide the CPU utilization for all Cassandra nodes in the analytics cluster over the last hour.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I present to the architecture review board, analyze the high CPU usage on node…+
Before I present to the architecture review board, analyze the high CPU usage on node 'database-node-7' that occurred last Tuesday. Identify the specific queries or operations that contributed most to the spike, so I can explain the root cause and proposed fixes clearly.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe reporting service is failing, and the CPU on our analytics Cassandra cluster is stuck at…+
The reporting service is failing, and CPU on the analytics cluster is pegged at 95%.
The reporting service is failing, and the CPU on our analytics Cassandra cluster is stuck at 95% across several nodes. I've checked for large queries, but nothing obvious stands out. I'm afraid this could bring down other dependent services. What's the most immediate action I can take to reduce the load, and what's the quickest way to identify the source of this high CPU?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently get pulled into investigating transient high CPU usage on Cassandra nodes, which…+
I spend too much time chasing down transient CPU spikes.
I frequently get pulled into investigating transient high CPU usage on Cassandra nodes, which often resolves itself before I can fully diagnose it. This wastes time and prevents me from focusing on strategic work. What routine check or monitoring adjustment can I implement to quickly identify the cause of these spikes, even if they're short-lived, without constant manual intervention?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Apache Cassandra's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.