◆ Apache Cassandra

Troubleshoot Cassandra repair hangs

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.

2prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AImprove — make it easier to acceptBefore I dive into this hanging repair on the 'analytics' keyspace, analyze the current cluster…+
Before I dive into this hanging repair on the 'analytics' keyspace, analyze the current cluster state. We've had issues where repairs hang due to network saturation or insufficient disk space. Suggest the most likely culprits and a diagnostic plan that prioritizes non-disruptive checks.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BDecide — diagnose the stuck momentThe repair for the 'events' keyspace has been stuck at 70% for three hours, and I've checked…+
The repair process for the 'events' keyspace has been stuck at 70% for the last 3 hours, and I can't find any obvious errors in the logs.
The repair for the 'events' keyspace has been stuck at 70% for three hours, and I've checked the node logs without seeing anything obvious. Our performance is starting to degrade, and I don't want to just kill the process without understanding why it's stuck. The SRE team is asking if it's safe to restart the node. What's the most likely reason for this silent hang, and what's the safest next step to get it moving without causing data inconsistency?
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.