◆ Apache Cassandra

Establish optimum database parameter values

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 taskSet the 'read_repair_chance' for the 'customer_data.users' table to…+
Set the 'read_repair_chance' for the 'customer_data.users' table to 0.1.
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 acceptOur cluster is experiencing intermittent high CPU usage and increased garbage collection…+
Our cluster is experiencing intermittent high CPU usage and increased garbage collection pauses, especially during peak hours. Before I suggest scaling up, analyze the current database parameter settings related to memory and compaction. Recommend changes that could alleviate the pressure and improve stability without adding more hardware.
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 cluster is reporting 'write timeouts' during our busiest marketing campaign, causing lost…+
The cluster is reporting 'write timeouts' during our busiest marketing campaign, causing lost customer data.
The cluster is reporting 'write timeouts' during our busiest marketing campaign, causing lost customer data and angry customers. The application team says they can't commit. I suspect the 'commitlog_sync_period_in_ms' is too aggressive or 'concurrent_writes' is too low, but I'm worried about data durability if I change them. We need to stabilize writes within the next hour. What's the safest parameter adjustment to prioritize write availability immediately without risking data loss?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI find myself constantly tweaking database parameters reactively to solve production issues,…+
I find myself constantly tweaking database parameters reactively to solve production issues.
I find myself constantly tweaking database parameters reactively to solve production issues, often under pressure, instead of having a stable, well-understood configuration. This leads to inconsistent performance and makes it hard to predict behavior. What habit should I change to establish more optimal and predictable database parameter values from the start, reducing firefighting?
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.