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

BUG 1858400: [Performance] Lease refresh period for machine-api-controllers is too high, causes heavy writes to etcd at idle #339

Merged

Conversation

Danil-Grigorev
Copy link

@Danil-Grigorev Danil-Grigorev commented Jul 20, 2020

The machine-api-controller components are refreshing their lease more
than all other components combined. Bringing this to 90s each, will
decrease etcd writes at idle.

Relevant MAO PR - openshift/machine-api-operator#649

@openshift-ci-robot openshift-ci-robot added bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Jul 20, 2020
@openshift-ci-robot
Copy link

@Danil-Grigorev: This pull request references Bugzilla bug 1858400, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.6.0) matches configured target release for branch (4.6.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

BUG 1858400: [Performance] Lease refresh period for machine-api-controllers is too high, causes heavy writes to etcd at idle

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@JoelSpeed
Copy link

/lgtm
Would it make sense to have a default for this in the MAO repo that can be vendored here? 🤔

@openshift-ci-robot
Copy link

@Danil-Grigorev: This pull request references Bugzilla bug 1858400, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.6.0) matches configured target release for branch (4.6.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

BUG 1858400: [Performance] Lease refresh period for machine-api-controllers is too high, causes heavy writes to etcd at idle

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@Danil-Grigorev
Copy link
Author

/retest

@Danil-Grigorev
Copy link
Author

/lgtm
Would it make sense to have a default for this in the MAO repo that can be vendored here? thinking

It may help, but re-vendor is always less visible and harder to track when then default value that will be set anyway in CLI.

The machine-api-controller components are refreshing their lease more
than all other components combined. Bringing this to 90s each, will
decrease etcd writes at idle.
@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Jul 20, 2020
@Danil-Grigorev
Copy link
Author

@JoelSpeed @enxebre NIT: fixed typo in the commit message. Please LGTM?..

@JoelSpeed
Copy link

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 20, 2020
@enxebre
Copy link
Member

enxebre commented Jul 20, 2020

the units are not passing

@Danil-Grigorev
Copy link
Author

the units are not passing

Seems like a race in unit tests, but I can't reproduce the issue locally. Give me a second to investigate.

@Danil-Grigorev
Copy link
Author

/retest

@Danil-Grigorev
Copy link
Author

@enxebre This should be the fix for the race in unit tests: #340

@JoelSpeed
Copy link

Seems like a race in unit tests, but I can't reproduce the issue locally. Give me a second to investigate.

I think this race may actually be fixed by #337 (I saw the error before and included a "fix"(?) for it in that PR)

@JoelSpeed
Copy link

Either way, the race is unrelated to the changes in this PR
/retest

@enxebre
Copy link
Member

enxebre commented Jul 21, 2020

/approve

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: enxebre

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 21, 2020
@openshift-merge-robot openshift-merge-robot merged commit 8e8db78 into openshift:master Jul 21, 2020
@openshift-ci-robot
Copy link

@Danil-Grigorev: Some pull requests linked via external trackers have merged: openshift/machine-api-operator#649, openshift/cluster-api-provider-ovirt#56, openshift/cluster-api-provider-openstack#109, openshift/cluster-api-provider-gcp#104, openshift/cluster-api-provider-baremetal#88. The following pull requests linked via external trackers have not merged:

In response to this:

BUG 1858400: [Performance] Lease refresh period for machine-api-controllers is too high, causes heavy writes to etcd at idle

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants