-
Notifications
You must be signed in to change notification settings - Fork 24.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GeoIpDownloader race conditions when starting / stopping #92888
Comments
Pinging @elastic/es-data-management (Team:Data Management) |
One of the biggest problems is that of of #76924 we are deleting the index when we stop the task. This is (I believe) so that we meet our license agreement for the geoip data and don't retain it too long. |
I meet a similar problem. when I start elasticsearch first time ,it runs without any error.
my server has enough space and cpu is 95% idle. |
I am also getting the same error when I install Elasticsearch, The error is : I read multiple comments on the Internet, they were referring me to disable "ingest. GeoIP.downloader.enabled" but this also could not resolve the error, Is anybody also facing the same issue? |
Hi folks
This is confusing for a newbie like me. Thanx and regards, |
Elasticsearch Version
8.7.0
Installed Plugins
No response
Java Version
bundled
OS Version
n/a
Problem Description
The geoip downloader has race conditions that can cause exceptions and unexpected behavior if it is stopped and started quickly. There are a few reasons for this, and they're not really easy to fix:
.geoip_databases
index asynchronously (added in Fix disabling GeoIP downloader through elasticsearch.yml #76924). If you re-start the downloader immediately, the delete can still be running when the start task is running, leading to an exception and missing a missinggeoip_databases
index.Here is a stack trace for problem # 1:
Here is a stack trace for problem # 3:
Steps to Reproduce
I added this to my local GeoIpDownloaderIT to reproduce this:
Logs (if relevant)
No response
The text was updated successfully, but these errors were encountered: