-
Notifications
You must be signed in to change notification settings - Fork 90
Bug 1908958: Change ElasticsearchClusterNotHealthy to 7 minutes #600
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 1908958: Change ElasticsearchClusterNotHealthy to 7 minutes #600
Conversation
|
/retest |
alanconway
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have an issue to figure out why this alert is coming up so often? Increasing the timeout might be a reasonable work-around, but it sounds like we should evaluate whether the alert itself should be removed or modified, or whether it's indicating something we need to fix.
|
@sedroche you will need to create a bz for 4.7 and clone for 4.6 if the intention is to pull this change into these releases. It is the only way to satisfy the workflow |
|
@sedroche: This pull request references Bugzilla bug 1908958, which is invalid:
Comment In response to this:
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. |
|
/bugzilla refresh |
|
@sedroche: This pull request references Bugzilla bug 1908958, which is invalid:
Comment In response to this:
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. |
|
/bugzilla refresh |
|
@sedroche: This pull request references Bugzilla bug 1908958, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
In response to this:
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. |
@jcantrill I have created a bz for 4.7 and 4.6 |
|
@sedroche: This pull request references Bugzilla bug 1908958, which is valid. 3 validation(s) were run on this bug
In response to this:
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. |
|
@sedroche: This pull request references Bugzilla bug 1908958, which is invalid:
Comment In response to this:
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. |
|
/bugzilla refresh |
|
@sedroche: This pull request references Bugzilla bug 1908958, which is valid. 3 validation(s) were run on this bug
In response to this:
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. |
|
/test cluster-logging-operator-e2e |
|
/bugzilla refresh |
|
@sedroche: This pull request references Bugzilla bug 1908958, which is valid. 3 validation(s) were run on this bug
In response to this:
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. |
|
@sedroche: The following test failed, say
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. |
|
@sedroche this looks to need a rebase |
fbb197f to
40a68d8
Compare
|
/retest |
1 similar comment
|
/retest |
|
@ewolinetz rebased |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alanconway, blockloop, ewolinetz, sedroche 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 |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@sedroche: All pull requests linked via external trackers have merged: Bugzilla bug 1908958 has been moved to the MODIFIED state. In response to this:
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. |
|
/cherrypick release-4.6 |
|
@jcantrill: #600 failed to apply on top of branch "release-4.6": In response to this:
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. |
Description
ElasticsearchClusterNotHealthyis one of the noisier alerts on OSD. After reviewing this alert we found that this alert "self resolves" most commonly after 5 minutes.Setting this to 7 minutes should relieve this.
/cc @alanconway
/assign @ewolinetz
Links
https://bugzilla.redhat.com/show_bug.cgi?id=1908958 4.7
https://bugzilla.redhat.com/show_bug.cgi?id=1908959 4.6