Elasticsearch didn't auto recover from disk space full

Elastic Stack Elasticsearch
1

I'm using ES 2.2.2, here is what i am confusing.

stages:

  1. ES running ok
  2. host space full
  3. ES running bad
  4. delete some nonsense logs
  5. ES still running bad(nested: AlreadyClosedException[translog is already closed]; )
  6. restart ES
  7. ES running ok!

I mean, shouldn't es will be ok after host disk space released?

Please remind me if you want more details.
Thanks.

2

Did you confirm that the disk space taken by the nonsense logs got released after you deleted them? Sometimes, filehandles stay open, especially for logs.

You can check them by doing the following on *nix systems!

$> sudo lsof +L1
3

Thanks your tip.
I didn't check the file handles, but other services in the same host recovered after files deleted. So i am sure it's not the reason.
Please note, i am using ES 2.x version.

Thanks.
Best regards.

4

any suggestion about this?

5

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.