◆ Elasticsearch

Set up an ES cluster

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 taskI need to set up a new three-node Elasticsearch cluster named 'dev-search' on our staging…+
I need to set up a new three-node Elasticsearch cluster named 'dev-search' on our staging environment. It should use the default port and have basic security enabled for our internal testing.
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 provision the new 'dev-search' cluster, help me ensure it's configured for high…+
Before I provision the new 'dev-search' cluster, help me ensure it's configured for high availability and efficient indexing of our product catalog data. I need to consider shard allocation, replica settings, and resource limits for the three nodes, anticipating future growth.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI'm trying to set up the 'customer-data' cluster for the new analytics project, but it keeps…+
The new cluster setup keeps failing after a few hours, and I'm getting vague error messages about resource limits.
I'm trying to set up the 'customer-data' cluster for the new analytics project, but it keeps failing after a few hours, giving vague errors about resource limits. The project lead needs it by end of day Friday, and I'm worried about over-provisioning and wasting resources, but also about under-provisioning and it failing again. I don't know if it's a memory issue, disk space, or something else. What's the likely diagnosis, and what's the best next move to get this cluster stable?
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 losing time and accuracy when setting up new clusters because I frequently misjudge…+
I frequently face issues with new cluster setups failing due to misconfigured resources.
I keep losing time and accuracy when setting up new clusters because I frequently misjudge resource requirements, leading to failures or over-provisioning. This impacts project timelines and our cloud spend. What habit should I change in my initial planning and configuration process to consistently set up stable and appropriately resourced clusters from the beginning?
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.