Skip to content
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

Optimize the per-document cluster state checks in the geoip and ip_location processors #121208

Open
joegallo opened this issue Jan 29, 2025 · 1 comment
Labels
:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP >enhancement Team:Data Management Meta label for data/management team

Comments

@joegallo
Copy link
Contributor

This is a continuation of #120824

  • We can use the threadpool's clocks rather than System.currentTimeInMillis() to get the time more efficiently.
  • We can use a better cluster state listener to:
    • watch for changes to the database_validity not-quite-Setting
    • update the map of database files
  • Also we currently call checkDatabases on every single cluster state change, that seems excessive.
@joegallo joegallo added :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP >enhancement Team:Data Management Meta label for data/management team labels Jan 29, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-data-management (Team:Data Management)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP >enhancement Team:Data Management Meta label for data/management team
Projects
None yet
Development

No branches or pull requests

2 participants