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

[Monitoring] Removing mappings.json from archive data is breaking tests #30152

Closed
chrisronline opened this issue Feb 5, 2019 · 2 comments
Closed
Labels
bug Fixes for quality problems that affect the customer experience Team:Monitoring Stack Monitoring team

Comments

@chrisronline
Copy link
Contributor

Related to elastic/elasticsearch#37773

In #29184, we had an issue where we tried to update our mappings.json for all our monitoring archives because Elasticsearch automatically inserts index templates for various .monitoring-* indices and these templates were conflicting with the updated mapping.json files we tried to use in #29184.

As a solution, we decided to just deleted all the mappings.json files and that seemed to work fine, but we've seen multiple bug reports (#29966, #29973) that are a result of this. Without a mappings.json file, the es archiver unload functionality does not properly delete the indices, leaving them in the functional test server for the next test suite which is causing unexpected results.

We need to restore these mappings.json and simply remove the mappings: { } section from each index in order to restore the es archiver unload delete functionality.

@chrisronline chrisronline added bug Fixes for quality problems that affect the customer experience Team:Monitoring Stack Monitoring team labels Feb 5, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/stack-monitoring

@chrisronline
Copy link
Contributor Author

cc @chrisdavies

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Team:Monitoring Stack Monitoring team
Projects
None yet
Development

No branches or pull requests

2 participants