◆ Apache Cassandra

Manage Cassandra maintenance

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
See the prompt↓All Apache Cassandra tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskRun the daily database compaction on the `customer_data` keyspace, prioritizing `orders` and…+
Run the daily database compaction on the `customer_data` keyspace, prioritizing `orders` and `inventory` tables, and then check for any dropped mutations by Friday morning.
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 run this week's database repair, make sure it won't impact our critical real-time…+
Before I run this week's database repair, make sure it won't impact our critical real-time services. Identify the busiest nodes and suggest a staggered repair schedule that keeps latency under 50ms for the `user_sessions` table.
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 `metrics` keyspace is showing high read latencies for the past hour, but the usual…+
The `metrics` keyspace is showing high read latencies for the past hour, but the usual compaction and repair jobs completed without errors.
The `metrics` keyspace is showing high read latencies for the past hour, but the usual compaction and repair jobs completed without errors. The ops team is getting alerts. I'm afraid to restart nodes without knowing why, and I can't see an obvious hot partition. Is this a data model issue or a resource bottleneck? What's the fastest way to diagnose and resolve this without causing an outage?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe keep having unexpected database performance dips after schema changes or data migrations. I…+
We keep having unexpected Cassandra performance dips after schema changes or data migrations.
We keep having unexpected database performance dips after schema changes or data migrations. I spend too much time firefighting these instead of building new features. What habit should I change to proactively identify and mitigate these performance risks before they hit production, especially when new large datasets are introduced?
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.