◆ Apache Cassandra

Tune Cassandra for production performance

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 taskAdjust the 'read_request_timeout_in_ms' to 5000 and 'write_request_timeout_in_ms' to 3000 for…+
Adjust the 'read_request_timeout_in_ms' to 5000 and 'write_request_timeout_in_ms' to 3000 for the 'api_data' keyspace on all nodes in the 'us-west-2' cluster.
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 we push the 'inventory_service' to production, make sure the cluster can handle 10,000…+
Before we push the 'inventory_service' to production, make sure the cluster can handle 10,000 writes per second and 5,000 reads per second with less than 10ms latency. We need to avoid any bottlenecks during peak sales events.
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 'session_store' cluster is showing intermittent high latencies, but CPU and disk I/O…+
We're seeing intermittent high latencies on our 'session_store' cluster, but CPU and disk I/O look normal. The application team is complaining about slow responses, but I can't pinpoint the cause.
The 'session_store' cluster is showing intermittent high latencies, but CPU and disk I/O metrics are stable. The application team is getting frustrated, but I can't find a clear bottleneck. I've checked basic configs, but I'm worried it's a subtle interaction I'm missing. What's the most likely culprit for this type of intermittent latency without obvious resource spikes, and what's the best next diagnostic step to isolate it?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI consistently struggle to proactively identify performance bottlenecks before they impact…+
I consistently struggle to proactively identify performance bottlenecks before they impact users, often reacting to incidents instead of preventing them.
I consistently struggle to proactively identify performance bottlenecks before they impact users, often reacting to incidents instead of preventing them. This leads to firefighting and impacts our team's reputation for reliability. What habit should I change in how I monitor and analyze cluster metrics to predict and address performance issues before they become critical?
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.