◆ Elasticsearch

Free store size after deleting documents

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 taskThe 'archive-logs' index on 'main-cluster' is full. Delete all documents older than 90 days…+
The 'archive-logs' index on 'main-cluster' is full. Delete all documents older than 90 days from this index to free up space immediately.
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 acceptWe're running low on disk space on 'main-cluster', and the 'archive-logs' index is the main…+
We're running low on disk space on 'main-cluster', and the 'archive-logs' index is the main culprit. Implement a strategy to regularly free up storage by deleting documents older than 90 days from 'archive-logs', ensuring the deletion process is efficient and doesn't impact cluster performance during peak hours. Verify the space is actually reclaimed.
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 just deleted a huge volume of old logs from 'archive-logs' on 'main-cluster' to free space,…+
I deleted millions of old documents from the 'archive-logs' index on 'main-cluster', but the disk space usage hasn't dropped significantly, and the cluster is still showing high utilization warnings.
I just deleted a huge volume of old logs from 'archive-logs' on 'main-cluster' to free space, but the disk usage hasn't budged, and the cluster is still red. I'm afraid I've missed a step or the space isn't actually being reclaimed. The ops team is getting alerts. What's the most common reason for this, and what's the immediate action I should take to force the space reclamation and stabilize the cluster?
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 getting caught off guard by the data store not immediately reclaiming disk space after…+
I frequently run into situations where deleting documents from Elasticsearch indexes doesn't immediately free up disk space, leading to unexpected storage issues.
I keep getting caught off guard by the data store not immediately reclaiming disk space after document deletions, leading to critical storage alerts and frantic troubleshooting. This pattern wastes valuable time. What habit should I change to ensure I consistently manage disk space effectively after deletions, avoiding these recurring storage crunch surprises?
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.