Add integration testing of microservices/replication for label queries #3130
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
To test the integration of the microservices in a similar to is actually run in the scalable/high availability setup. After the cluster is fully started, it pushes profiles for a number of services and then queries the series, label names and label values. It then stops one instance each to ensure it is still queryable wihtout data loss.
simonswine
force-pushed
the
20240322_improve-integration-test-with-microservices
branch
from
b7cbb34
to
9f35982
Compare
simonswine
changed the title
|
I think the current state contains something that is already mergable, I would like to see how stable the test is and then potentially extend the coverage. |
This causes a data race
kolesnikovae
approved these changes
Apr 1, 2024
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.
I am currently trying to understand some behaviour while running with an unhealthy ingester/store-gateway each.
For this purpose I've create this testing helper that can spin up multiple microservices locally.