◆ Apache Cassandra

Perform nodetool cleanup

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 nodetool cleanup on node 'database-node-7' in datacenter2 to reclaim disk space after…+
Perform a nodetool cleanup on node 'database-node-7' in datacenter2 to reclaim disk space after a recent data deletion.
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 the next nodetool cleanup across the 'user_data' keyspace, analyze the current…+
Before I run the next nodetool cleanup across the 'user_data' keyspace, analyze the current disk usage and tombstone ratios across all nodes. Recommend a cleanup strategy that minimizes I/O impact during business hours and prioritizes nodes with the most reclaimable space, and flag any potential issues with large partition tombstones.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI just ran a nodetool cleanup on 'database-node-5' after deleting a large amount of historical…+
I ran a nodetool cleanup, but disk space hasn't been reclaimed as expected.
I just ran a nodetool cleanup on 'database-node-5' after deleting a large amount of historical data, but the disk usage metrics haven't significantly dropped. I'm worried about running out of space before the end of the month, and the operations manager is asking why the cleanup wasn't effective. What's the most likely diagnosis for the un-reclaimed space, and what's my best next move to ensure the disk space is actually freed up without impacting live traffic?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly battling disk space issues after data purges or TTL expirations, often needing…+
I consistently struggle with managing disk space efficiently after data deletions.
I'm constantly battling disk space issues after data purges or TTL expirations, often needing emergency nodetool cleanups. This reactive approach consumes valuable time and adds unnecessary risk. What habit should I change to proactively manage disk space and ensure efficient reclamation after data deletions, so I'm not always scrambling to free up space?
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.