◆ Apache Cassandra

Perform routine Cassandra maintenance tasks

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 taskRun a major compaction on the 'customer_data' keyspace on all nodes in the 'us-east-1'…+
Run a major compaction on the 'customer_data' keyspace on all nodes in the 'us-east-1' datacenter by Friday.
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 our annual audit, I need to ensure our 'financial_transactions' cluster is optimally…+
Before our annual audit, I need to ensure our 'financial_transactions' cluster is optimally maintained. I'm worried about data consistency, potential disk space issues from old snapshots, and ensuring our backups are valid. Help me review our current maintenance schedule and suggest any critical tasks or adjustments needed to guarantee data integrity and operational readiness for the audit.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOne of our Cassandra nodes just reported high disk usage and a 'compaction_pending' metric…+
One of our Cassandra nodes just reported high disk usage and a 'compaction_pending' metric that's continuously climbing.
One of our Cassandra nodes just reported high disk usage and a 'compaction_pending' metric that's continuously climbing, even though we have regular scheduled compactions. I'm afraid this node will run out of disk space or become unresponsive, and I can't let the service go down. What's the likely diagnosis for this persistent backlog, and what's the best next move to clear it safely and prevent recurrence?
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 find myself manually intervening in data storage maintenance tasks because…+
I frequently find myself manually intervening in Cassandra maintenance tasks because automated scripts fail or don't cover specific edge cases.
I frequently find myself manually intervening in data storage maintenance tasks because automated scripts fail or don't cover specific edge cases, leading to inconsistent cluster health and wasted time. I need to improve the reliability and completeness of our automated maintenance. What habit should I change to ensure our routine data storage maintenance tasks are consistently executed and effective without constant manual oversight?
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.