◆ Elasticsearch

Move Elasticsearch data between servers

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 taskMove all data from the old server 'es-old-01' to the new server 'es-new-01'. Ensure all indices…+
Move all data from the old server 'es-old-01' to the new server 'es-new-01'. Ensure all indices are replicated completely and then remove them from the old server once verified.
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 move all the data from the old server to the new one, make sure this process is…+
Before I move all the data from the old server to the new one, make sure this process is transparent to users. I need it to happen without any downtime, and I want to verify data integrity before the old server is decommissioned. Also, give me a rollback plan in case something goes wrong during the transfer.
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 data transfer from 'es-old-02' to 'es-new-02' has been stuck at 70% for the last hour, and…+
Data transfer between Elasticsearch servers is stuck, and I don't know why.
The data transfer from 'es-old-02' to 'es-new-02' has been stuck at 70% for the last hour, and I'm getting 'cluster health red' errors on the new server. The logs show some unassigned shards, but I can't tell if it's a disk space issue on the new machine or a network problem between them. We have a maintenance window ending in two hours. What's the most likely cause, and what's the fastest way to get this moving again without risking data loss or a full rollback?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery time I need to move data between servers, it feels like a high-stakes gamble. I spend too…+
Moving Elasticsearch data between servers is always a high-stress event.
Every time I need to move data between servers, it feels like a high-stakes gamble. I spend too much time manually checking shard allocations, worrying about data consistency, and dealing with unexpected network hiccups. I lose sleep over potential data loss or extended downtime. What habit can I change to make these data migrations between servers more predictable, less stressful, and consistently reliable?
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.