Skip to content

Cherry-pick #22357 to 7.x: Add warning about setup.template.overwrite to documentation and reference configuration#22415

Merged
kvch merged 1 commit intoelastic:7.xfrom
kvch:backport_22357_7.x
Nov 6, 2020
Merged

Cherry-pick #22357 to 7.x: Add warning about setup.template.overwrite to documentation and reference configuration#22415
kvch merged 1 commit intoelastic:7.xfrom
kvch:backport_22357_7.x

Conversation

@kvch
Copy link
Copy Markdown
Contributor

@kvch kvch commented Nov 4, 2020

Cherry-pick of PR #22357 to 7.x branch. Original message:

What does this PR do?

This PR adds a warning about setup.template.overwrite option.

Why is it important?

Users might enable this option and then start multiple instances of Beats at the same time. This can overload Elasticsearch with too many template update requests.

Checklist

- [ ] My code follows the style guidelines of this project
- [ ] I have commented my code, particularly in hard-to-understand areas

  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
    - [ ] I have added tests that prove my fix is effective or that my feature works
    - [ ] I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

@kvch kvch requested review from a team as code owners November 4, 2020 13:30
@kvch kvch added [zube]: In Review backport Team:Services (Deprecated) Label for the former Integrations-Services team labels Nov 4, 2020
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Nov 4, 2020
@elasticmachine
Copy link
Copy Markdown
Contributor

Pinging @elastic/integrations-services (Team:Services)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Nov 4, 2020
…ence configuration (elastic#22357)

This PR adds a warning about `setup.template.overwrite` option.

Users might enable this option and then start multiple instances of Beats at the same time. This can overload Elasticsearch with too many template update requests.

(cherry picked from commit 8798d41)
@kvch kvch force-pushed the backport_22357_7.x branch from 97b8097 to 3b75914 Compare November 4, 2020 13:32
Copy link
Copy Markdown
Contributor

@michalpristas michalpristas left a comment

Choose a reason for hiding this comment

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

Backport looks good,

@elasticmachine
Copy link
Copy Markdown
Contributor

elasticmachine commented Nov 4, 2020

💚 Flaky test report

Tests succeeded.

Expand to view the summary

Test stats 🧪

Test Results
Failed 0
Passed 16365
Skipped 1367
Total 17732

@elasticmachine
Copy link
Copy Markdown
Contributor

elasticmachine commented Nov 4, 2020

💚 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

Expand to view the summary

Build stats

  • Build Cause: [kvch commented: jenkins run tests]

  • Start Time: 2020-11-06T10:56:34.869+0000

  • Duration: 89 min 16 sec

Test stats 🧪

Test Results
Failed 0
Passed 16365
Skipped 1367
Total 17732

@kvch
Copy link
Copy Markdown
Contributor Author

kvch commented Nov 6, 2020

jenkins run tests

@kvch kvch merged commit 6668a16 into elastic:7.x Nov 6, 2020
@zube zube bot removed the [zube]: Done label Feb 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport Team:Services (Deprecated) Label for the former Integrations-Services team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants