Skip to content
This repository has been archived by the owner on Aug 25, 2021. It is now read-only.

catalog sync use too much of CPU #83

Closed
kgignatyev-inspur opened this issue Dec 8, 2018 · 3 comments
Closed

catalog sync use too much of CPU #83

kgignatyev-inspur opened this issue Dec 8, 2018 · 3 comments

Comments

@kgignatyev-inspur
Copy link

I have deployed the helmchart and disabled everything except sync from k8s to Consul (k8s is running in Docker CE app locally) and all is working BUT CPU consumption shoot to the moon the moment this is deployed.
image

the moment the helm chart is undeployed CPU utilization goes back to normal
image

@adilyse
Copy link
Contributor

adilyse commented Dec 8, 2018

Hi @kgignatyev-inspur,

Could you post the version of the helm chart and consul-k8s you're using, as well as the sync settings in the values file? That will help narrow down what might be going on.

@kgignatyev-inspur
Copy link
Author

here it is, note that the values file has customizations
consul-helm.zip

@adilyse
Copy link
Contributor

adilyse commented Feb 5, 2019

Good catch! There was a hot loop for syncing Kubernetes services to Consul. This has now been fixed and should be included in the next release.

@adilyse adilyse closed this as completed Feb 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants