◆ Apache Cassandra

Perform Apache 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 taskPerform a rolling restart of the Cassandra cluster in the staging environment tonight at 2 AM,…+
Perform a rolling restart of the Cassandra cluster in the staging environment tonight at 2 AM, ensuring all nodes come back online and data consistency is maintained, then send a confirmation to the operations team.
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 do the rolling restart of the production Cassandra cluster, make sure I have a clear…+
Before I do the rolling restart of the production Cassandra cluster, make sure I have a clear rollback plan, flag any nodes that are currently under heavy load, and check the current data replication status to avoid any data loss or service disruption.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA critical Cassandra node just unexpectedly went down during our routine compaction…+
A critical node just went down during a routine Cassandra maintenance operation, and services are degrading.
A critical Cassandra node just unexpectedly went down during our routine compaction maintenance, and now the dashboard is showing service degradation for customer-facing applications. I'm afraid if another node fails, we'll have a full outage, and I can't tell the incident manager we were just doing 'routine' work. Was this an issue with the compaction itself or an underlying hardware problem? What's the immediate best next move to stabilize the cluster and prevent further impact?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOur distributed NoSQL database maintenance tasks, like compaction and upgrades, consistently…+
Our Cassandra maintenance tasks frequently cause unexpected issues or require extensive manual oversight, leading to stress and late nights.
Our distributed NoSQL database maintenance tasks, like compaction and upgrades, consistently lead to unexpected issues or require meticulous manual oversight, often resulting in late-night calls and high stress for the team. We're always reacting to problems instead of preventing them. What habit should I change in how we plan and execute these operations to make them more predictable, automated, and less prone to causing incidents?
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.