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

kafka replay speed: upstream local development environment #9455

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

dimitarvdimitrov
Copy link
Contributor

What this PR does

This is the fourth of series of PRs to upstream the code for improving Kafka replay speed in the ingester.

This PR makes several changes to development/mimir-ingest-storage

  • deploys a jaeger instance to collect traces
  • deploys ingester-zone-c-61. This ingester is totally separate from the other two zones. The idea is to be able to feed its partition with old data and test replay speed. That ingester doesn't ingest metrics from the cluster itself, so being down doesn't affect the cluster's query availability
  • deploys 3 kafkas with RF=2 so that we can bring down brokers and test how our code reacts to leader reelections
  • optinally enabled dlv debugging for the Mimir images
  • configures ingesters to use concurrent fetching

Which issue(s) this PR fixes or relates to

Fixes #

Checklist

  • Tests updated.
  • Documentation added.
  • CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX].
  • about-versioning.md updated with experimental features.

This PR makes several changes to development/mimir-ingest-storage

* deploys a jaeger instance to collect traces
* deploys ingester-zone-c-61. This ingester is totally separate from the other two zones. The idea is to be able to feed its partition with old data and test replay speed. That ingester doesn't ingest metrics from the cluster itself, so being down doesn't affect the cluster's query availability
* deploys 3 kafkas with RF=2 so that we can bring down brokers and test how our code reacts to leader reelections
* optinally enabled dlv debugging for the Mimir images
* configures ingesters to use concurrent fetching

Signed-off-by: Dimitar Dimitrov <dimitar.dimitrov@grafana.com>
@dimitarvdimitrov dimitarvdimitrov requested a review from a team as a code owner September 27, 2024 16:33
Comment on lines 38 to 45
}],
[{
__address__ = "mimir-write-zone-c-61:8080",
cluster = "docker-compose",
container = "mimir-write",
namespace = "mimir-read-write-mode",
job = "mimir-write-zone-c",
}],
Copy link
Contributor

Choose a reason for hiding this comment

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

(nit) Seems that tabs and spaces are mixed in this config here, right? ;)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

i think it's only using spaces.. i asked goland to convert "to spaces" and it said it's already formatted. i fixed the indentation of this line in the meantime

Copy link
Contributor

Choose a reason for hiding this comment

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

@dimitarvdimitrov have you forgotten to push the changes, maybe? The indentation is still off here ;)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

this is what i pushed f5b6bcb
Screenshot 2024-10-10 at 11 19 41

i think GH doesn't update the diff on the comment

Signed-off-by: Dimitar Dimitrov <dimitar.dimitrov@grafana.com>
Signed-off-by: Dimitar Dimitrov <dimitar.dimitrov@grafana.com>
Copy link
Contributor

@narqo narqo left a comment

Choose a reason for hiding this comment

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

🔥 Besides the broken indentation, the changes work for me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants