◆ Apache Cassandra

Change Cassandra compaction strategy

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 taskChange the compaction strategy for the 'events_log' table in the 'telemetry' keyspace to…+
Change the compaction strategy for the 'events_log' table in the 'telemetry' keyspace to 'TimeWindowCompactionStrategy' with a window size of 1 day and a tombstone compaction interval of 30 minutes, then monitor its impact on disk usage and read latency.
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 switch the 'user_sessions' table to 'DateTieredCompactionStrategy', analyze its…+
Before I switch the 'user_sessions' table to 'DateTieredCompactionStrategy', analyze its current read/write patterns and data retention policy. Recommend the optimal min_sstable_size and max_sstable_age_days to balance disk space, read performance, and compaction overhead for our typical access patterns.
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_data' table's disk usage just jumped 30% in two hours, and read latencies are…+
The 'metrics_data' table's disk usage is spiking after a recent traffic surge, and our current compaction strategy isn't keeping up, leading to high read latencies.
The 'metrics_data' table's disk usage just jumped 30% in two hours, and read latencies are through the roof. The current 'SizeTieredCompactionStrategy' isn't handling the burst writes well, and I'm worried about hitting disk limits on the nodes by end of day. I can't tell if changing to 'LeveledCompactionStrategy' will fix it quickly enough or just make the situation worse with more I/O. What's the fastest, safest compaction strategy change to get disk usage under control and restore read performance without causing more I/O bottlenecks?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe consistently find ourselves scrambling to adjust compaction strategies whenever disk usage…+
We're always reacting to compaction issues, either high disk usage or slow reads, instead of proactively managing them.
We consistently find ourselves scrambling to adjust compaction strategies whenever disk usage or read latency becomes a problem, often under pressure from the SRE team. It feels like we're always one step behind. What habit should I change to proactively select and tune compaction strategies for new and existing tables, so we avoid these reactive crises?
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.