◆ Elasticsearch

Fix unassigned Elasticsearch shards

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 taskFix the unassigned Elasticsearch shards on the 'customer_logs_2024_05' index by reallocating…+
Fix the unassigned Elasticsearch shards on the 'customer_logs_2024_05' index by reallocating them to available data nodes. Prioritize nodes with less than 70% disk utilization.
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 reallocate the unassigned shards on 'customer_logs_2024_05', tell me why they became…+
Before I reallocate the unassigned shards on 'customer_logs_2024_05', tell me why they became unassigned. I need to know if it was a node failure, disk space, or something else, so I can prevent it from happening again. Also, suggest the best strategy to reassign them without causing further cluster instability.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentWe're seeing a sudden spike in unassigned shards across several critical indices after what…+
I'm seeing a sudden spike in unassigned shards across multiple indices, and I can't pinpoint the cause.
We're seeing a sudden spike in unassigned shards across several critical indices after what seemed like a routine node restart this morning. I've checked disk space and basic node health, but nothing obvious explains why so many shards are stuck. I'm worried about data loss and performance degradation. What's the most likely diagnosis here, and what's the fastest way to stabilize the cluster without making things worse?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm spending too much time manually fixing unassigned shards after every minor outage or…+
I spend too much time manually fixing unassigned shards after routine maintenance or minor outages.
I'm spending too much time manually fixing unassigned shards after every minor outage or routine maintenance. It feels like I'm always reacting to these issues instead of having a resilient system. What habit should I change to proactively prevent unassigned shards or ensure they self-heal more effectively, reducing my manual intervention time?
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.