◆ Apache Cassandra

Troubleshoot Cassandra server errors

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 taskCheck the logs on node 10.0.0.5 for any 'OutOfMemoryError' messages from the last 24 hours and…+
Check the logs on node 10.0.0.5 for any 'OutOfMemoryError' messages from the last 24 hours and report the timestamps and specific error details.
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 acceptWhen a node goes down, I want to quickly understand if it's a network issue, a disk failure, or…+
When a node goes down, I want to quickly understand if it's a network issue, a disk failure, or a JVM problem. Improve my diagnostic steps to first check connectivity, then disk health, then JVM logs, giving me a clear indication of where to focus my deeper troubleshooting.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentNode 10.0.0.7 just stopped responding to client requests, but the operating system reports it's…+
Node 10.0.0.7 just stopped responding to client requests, but the operating system reports it's still running.
Node 10.0.0.7 just stopped responding to client requests, but the operating system reports it's still running. There are no obvious errors in the application logs, and other nodes in the datacenter are fine. I'm afraid this could be a hung process or a network partition, and I can't risk a full restart without knowing why it's unresponsive. What's the most likely diagnosis, and what's the safest first step to get it back online without data loss?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI spend too much time manually sifting through logs to pinpoint root causes of node failures,…+
I spend too much time manually sifting through logs to pinpoint root causes of node failures.
I spend too much time manually sifting through logs to pinpoint root causes of node failures, especially when dealing with intermittent issues or subtle performance degradations. This delays resolution and impacts application uptime. What habit should I change in how I approach log analysis and monitoring to more quickly identify and diagnose server errors?
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.