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

[7.x](backport #26952) Adding functionality to death letter index instead of dropping events. #27201

Merged
merged 1 commit into from
Aug 3, 2021

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Aug 2, 2021

This is an automatic backport of pull request #26952 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.io/

Adding functionality to death letter index instead of dropping events.

When there's a mapping conflict events are dropped, this commits allows one attempting to index it into a different index instead so it can be re-ingested later vs dropping or stalling ingest. The index currently must reside on the same ES cluster.

* buildCollectPublishFails and other functions changed to be a function of Client so not to have to pass arguments

Co-authored-by: Noémi Ványi <[email protected]>
(cherry picked from commit 60cf09d)
@mergify mergify bot added the backport label Aug 2, 2021
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Aug 2, 2021
@botelastic
Copy link

botelastic bot commented Aug 2, 2021

This pull request doesn't have a Team:<team> label.

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2021-08-02T18:21:35.247+0000

  • Duration: 150 min 28 sec

  • Commit: d18dc64

Test stats 🧪

Test Results
Failed 0
Passed 48851
Skipped 5267
Total 54118

Trends 🧪

Image of Build Times

Image of Tests

💚 Flaky test report

Tests succeeded.

Expand to view the summary

Test stats 🧪

Test Results
Failed 0
Passed 48851
Skipped 5267
Total 54118

@kvch kvch merged commit e3942d5 into 7.x Aug 3, 2021
@mergify mergify bot deleted the mergify/bp/7.x/pr-26952 branch August 3, 2021 09:19
@mergify
Copy link
Contributor Author

mergify bot commented Nov 1, 2021

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b mergify/bp/7.x/pr-26952 upstream/mergify/bp/7.x/pr-26952
git merge upstream/7.x
git push upstream mergify/bp/7.x/pr-26952

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants