[Alerting] Shift polling interval by random amount when Task Manager experiences consistent claim version conflicts #88020
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gmmorris
changed the title
gmmorris
added
Feature:Alerting
release_note:fix
Team:ResponseOps
|
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
gmmorris
commented
Jan 12, 2021
ymao1
reviewed
Jan 12, 2021
gmmorris
commented
Jan 12, 2021
x-pack/plugins/task_manager/server/polling/delay_on_claim_conflicts.ts
Outdated
Show resolved
Hide resolved
mikecote
approved these changes
Jan 12, 2021
pmuellr
approved these changes
Jan 12, 2021
…mmorris/kibana into tm/shift-polling-on-persistent-clashes * 'tm/shift-polling-on-persistent-clashes' of github.com:gmmorris/kibana: typo
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: |
gmmorris
added a commit
to gmmorris/kibana
that referenced
this pull request
Jan 12, 2021
…experiences consistent claim version conflicts (elastic#88020) This PR Introduces a `pollingDelay` which is applied to the polling interval whenever the average percentage of tasks experiencing a version conflict is higher than a preconfigured threshold (default to 80%).
gmmorris
added a commit
to gmmorris/kibana
that referenced
this pull request
Jan 12, 2021
…experiences consistent claim version conflicts (elastic#88020) This PR Introduces a `pollingDelay` which is applied to the polling interval whenever the average percentage of tasks experiencing a version conflict is higher than a preconfigured threshold (default to 80%).
|
Added Docs for this into the Scaling docs in ad4fde6 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Closes #87808
This PR Introduces a
pollingDelaywhich is applied to the polling interval whenever the average percentage of tasks experiencing a version conflict is higher than a preconfigured threshold (default to 80%).Notes:
delayOnClaimConflictsfunction and the Monitoring Stats components. I've kept these apart on purpose to avoid changing unnecessary code as part of this PR due to it being a post-FF fix.Checklist
Delete any items that are not applicable to this PR.
Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n supportAny UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)This was checked for cross-browser compatibilityFor maintainers