◆ Apache Cassandra

Address Cassandra slow reads

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 taskInvestigate why the 'user_sessions' table reads are consistently over 500ms for the past hour…+
Investigate why the 'user_sessions' table reads are consistently over 500ms for the past hour and provide the top three most likely causes and immediate steps to mitigate them before the morning traffic spike.
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 peak user load tomorrow, analyze the 'product_catalog' table's read performance.…+
Before our peak user load tomorrow, analyze the 'product_catalog' table's read performance. Suggest three specific improvements to reduce latency, focusing on changes that won't require application code redeployment.
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 'order_history' table reads just spiked to 2 seconds, and the ops team is asking why. I'm…+
The 'order_history' table reads just spiked to 2 seconds, and the ops team is asking why.
The 'order_history' table reads just spiked to 2 seconds, and the ops team is asking why. I'm afraid this will impact our critical business reporting and I don't know if it's a sudden load increase or a node issue. What's the most likely diagnosis for this sudden spike, and what's the best first step to get it back under 500ms without causing more instability?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep getting pulled into urgent calls about slow reads on critical tables, often after hours,…+
I keep getting pulled into urgent calls about slow reads on critical tables, often after hours.
I keep getting pulled into urgent calls about slow reads on critical tables, often after hours, because I'm always reacting to symptoms. What habit should I change to proactively identify and address potential read bottlenecks before they impact users and trigger alerts?
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.