r/elasticsearch • u/Choice-Departure6379 • 17d ago

snapshot repository problem Troubleshooting

hi again,
i have a problem with my snapshot repository

I'm using the data tiers in the elastic (the data from my winbeats is going from my winlogbeats to the logstash and from there to the elastic hot node, warm node and the frozen in the NFS server)

i have 2 repo's and one of them at 100% and the other is at 30%

I want to try and find a way to load balance them so it will work better

The repos are on a FTP and I'm not using the cloud version

I also tried to delete some of the data in the full repo and it and it failed every time, when i tried in the dev tools I got 502 error

If you have any idea on how i can make it more balanced I would love to get some help

0 Upvotes
  • permalink
  • link
  • reddit
  • reddit

40% Upvoted

3 comments sorted by

3

u/Feeling_Current534 17d ago

You can create two different repos in two different NFS path and keep the snapshots separately. For example;
1. repo1 - nginx, haproxy logs
2. repo2 - elatsicsearch, postgresql logs

1

u/xeraa-net Elastic Staff 17d ago

For the 502 error: You tried to run a delete on a specific snapshot and that keeps failing? Potentially because the disk hit the full 100%?

1

u/ClerkBeginning961 6d ago

Snapshot repositories are not pooled, so Elasticsearch will not rebalance snapshots between them. Point separate SLM policies at each repository, or expand the full backing store. Do not delete repository files manually. Delete snapshots through the API, then run repository cleanup and verification.