-
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
Discovery GCE Pagination Lack #83783
Labels
>bug
:Distributed/Discovery-Plugins
Anything related to our integration plugins with EC2, GCP and Azure
Team:Distributed
Meta label for distributed team
Comments
Pinging @elastic/es-distributed (Team:Distributed) |
arteam
pushed a commit
to arteam/elasticsearch
that referenced
this issue
Feb 15, 2022
elastic#83785) Discovery gce plugin has some issues while running in large pools of vms instances. This pr attempts to solve it. Closes elastic#83783
arteam
pushed a commit
to arteam/elasticsearch
that referenced
this issue
Feb 15, 2022
elastic#83785) Discovery gce plugin has some issues while running in large pools of vms instances. This pr attempts to solve it. Closes elastic#83783
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
>bug
:Distributed/Discovery-Plugins
Anything related to our integration plugins with EC2, GCP and Azure
Team:Distributed
Meta label for distributed team
Elasticsearch Version
All
Installed Plugins
discovery-gce
Java Version
bundled
OS Version
any
Problem Description
Currently, discovery-gce plugin tries to obtain all instances for a given project/zone in one shot.
Recently I've faced in my company (that had ~ 700 instances running at the time) a weird behavior of this plugin. The google api that this plugin uses paginates results in chunks of 500 items. The current implementation is ignoring if there's a next page available.
Steps to Reproduce
Logs (if relevant)
No response
The text was updated successfully, but these errors were encountered: