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] Increase leader elect retry period to 90s #116

Closed
wants to merge 1 commit into from

Conversation

elmiko
Copy link

@elmiko elmiko commented Aug 27, 2020

What this PR does / why we need it:
This change increases the leader election retry period to 90s. This
change is being made to reduce the number of updates that can occur to
etcd in a worst case leader election scenario.

This was supposed to be part of #114 , but got missed due to a copy-paste error.

Which issue(s) this PR fixes
Bugzilla 1858400

This change increases the leader election retry period to 90s. This
change is being made to reduce the number of updates that can occur to
etcd in a worst case leader election scenario.
@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 Aug 27, 2020
@openshift-ci-robot
Copy link

@elmiko: 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] Increase leader elect retry period to 90s

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.

@openshift-ci-robot
Copy link

@elmiko: 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] Increase leader elect retry period to 90s

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.

Copy link

@michaelgugino michaelgugino left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci-robot
Copy link

@michaelgugino: changing LGTM is restricted to collaborators

In response to this:

/lgtm

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.

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: elmiko, michaelgugino
To complete the pull request process, please assign iamemilio
You can assign the PR to them by writing /assign @iamemilio in a comment when ready.

The full list of commands accepted by this bot can be found 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

@Danil-Grigorev
Copy link

@elmiko
Copy link
Author

elmiko commented Aug 27, 2020

@michaelgugino @elmiko Just wanted to mention - openshift/cluster-api-provider-baremetal#100 (comment)

that's a good point Danil, i'm going to put a hold on this until we figure out the proper value
/hold

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 27, 2020
@openshift-ci-robot
Copy link

@elmiko: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-openstack 16fd74a link /test e2e-openstack

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@elmiko
Copy link
Author

elmiko commented Aug 27, 2020

we discussed this as a group and we are in agreement that the 20s retry period is fine for now. i am closing this pr

@elmiko elmiko closed this Aug 27, 2020
@openshift-ci-robot
Copy link

@elmiko: This pull request references Bugzilla bug 1858400. The bug has been updated to no longer refer to the pull request using the external bug tracker.

In response to this:

BUG 1858400: [Performance] Increase leader elect retry period to 90s

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.

@elmiko elmiko deleted the update-retry-period branch August 27, 2020 15:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants