[
https://issues.apache.org/jira/browse/KAFKA-9059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16962152#comment-16962152
]
ASF GitHub Bot commented on KAFKA-9059:
---------------------------------------
viktorsomogyi commented on pull request #7609: KAFKA-9059: Implement
ReassignmentMaxLag
URL: https://github.com/apache/kafka/pull/7609
This PR implements the
kafka.server:type=ReplicaManager,name=ReassignmentMaxLag,clientId=Leader metric
by keeping track of the reassignment lag in the follower.
### Committer Checklist (excluded from commit message)
- [ ] Verify design and implementation
- [ ] Verify test coverage and CI build status
- [ ] Verify documentation (including upgrade notes)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Implement ReassignmentMaxLag
> ----------------------------
>
> Key: KAFKA-9059
> URL: https://issues.apache.org/jira/browse/KAFKA-9059
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 2.5.0
> Reporter: Viktor Somogyi-Vass
> Assignee: Viktor Somogyi-Vass
> Priority: Major
>
> Some more thinking is required to the implementation of MaxReassignmentLag
> proposed by
> [KIP-352|https://cwiki.apache.org/confluence/display/KAFKA/KIP-352:+Distinguish+URPs+caused+by+reassignment]
> as it's not so straightforward (need to maintain partitions' lag), therefore
> we separated it off into this JIRA.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
