◆ Elasticsearch

Configure shards and replicas

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 taskConfigure the 'customer-data' index to have 3 primary shards and 1 replica for each…+
Configure the 'customer-data' index to have 3 primary shards and 1 replica for each shard.
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 adjust the shard and replica count for our 'order-history' index, help me figure out…+
Before I adjust the shard and replica count for our 'order-history' index, help me figure out the right balance. We're seeing slow search performance but don't want to over-provision and waste resources. What metrics should I analyze to determine the optimal number of shards for query speed and replicas for high availability, given our current data volume and expected growth for next quarter?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur 'metrics-daily' index is showing high disk usage and slow indexing performance, but I'm…+
Our 'metrics-daily' index is showing high disk usage and slow indexing performance, but I'm hesitant to change shard count.
Our 'metrics-daily' index is showing high disk usage and slow indexing performance, but I'm hesitant to change the shard count because I'm afraid of causing data loss or an outage during the re-sharding process. We also have a critical report due Tuesday that relies on this data. What's the safest and most efficient way to address the performance issues without jeopardizing data integrity or the report deadline?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently find myself reacting to performance issues by adjusting shard and replica counts…+
I frequently find myself reacting to performance issues by adjusting shard/replica counts under pressure.
I frequently find myself reacting to performance issues by adjusting shard and replica counts under pressure, often after problems have already impacted users. This reactive approach leads to rushed decisions and potential instability. What habit can I change in my monitoring or planning process to proactively anticipate scaling needs for our indices and make these configuration changes before they become emergencies?
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 Elasticsearch'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.