Loading...

XML

Word

Printable

Type: Task
Resolution: Won't Do
Priority: Major
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
- kafka-integrations-apac-refinement-done
- kafka-integrations-europe-refinement-done

Epic Link:
Reduce time taken for followers to catch-up
Blocked:
False
Blocked Reason:
None
Ready:
False
Discussed with Team:
No
Feature Link:
MGDSRVS-48 - Be able to sustain an external paying customer in production
[QE] How to address?:
---
[QE] Why QE missed?:
---

Sprint:
MK - Sprint 225

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

WHAT

Potentially a one shot job to determine the number of replica fetcher threads.

WHY

To have a deterministic way of measuring the affect of changing the number of replica fetcher threads.

HOW

The test might do the following steps:

User perf tests to generate load.
Update broker configuration
Add additional replicas
Measure time to additional replicas joining ISR

depends on

MGDSTRM-9541 Determine how to update and monitor number of replica fetchers

Closed

is depended on by

MGDSTRM-9020 determine a better `num.replica.fetchers` value in kafka broker

Closed

Assignee:: Sam Barker

Reporter:: Sam Barker

Contributors:: Luke Chen, Robert Young

Team:: Kafka Integrations

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2022/08/29 10:49 PM

Updated:: 2022/09/23 4:52 AM

Resolved:: 2022/09/23 4:52 AM