◆ Apache Cassandra

Troubleshoot common Cassandra problems

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 taskTroubleshoot the 'node03' Cassandra instance in the 'payment_processing' cluster; it's showing…+
Troubleshoot the 'node03' Cassandra instance in the 'payment_processing' cluster; it's showing high CPU usage and connection timeouts in the logs since 2 PM.
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 acceptThe 'user_profiles' cluster is experiencing elevated read latencies across all nodes. Before I…+
The 'user_profiles' cluster is experiencing elevated read latencies across all nodes. Before I dive into individual logs, analyze the recent changes to the application's read patterns and the database's configuration. Suggest the top three most probable causes and a prioritized plan for investigation, considering our need for minimal downtime.
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 nightly analytics batch job failed again with 'ReadTimeoutException' for the…+
The nightly batch job for analytics failed again with 'ReadTimeoutException', but the cluster looked fine during the day.
The nightly analytics batch job failed again with 'ReadTimeoutException' for the 'daily_metrics' table, but during the day, the cluster seemed stable. I'm afraid this recurring issue is delaying critical business intelligence reports. I can't tell if it's a specific query pattern, a compaction issue, or resource contention during the batch window. What's the most likely cause, and what's the safest first step to debug this without impacting the real-time services running on the same cluster?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep losing time chasing intermittent database problems that seem to resolve themselves…+
I spend too much time chasing intermittent Cassandra issues that seem to disappear before I can fully diagnose them.
I keep losing time chasing intermittent database problems that seem to resolve themselves before I can get a clear picture, only to reappear later. This makes me feel like I'm always playing whack-a-mole. What habit should I change to better capture and analyze transient database issues, so I can diagnose root causes more effectively?
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.