elkkhan opened a new pull request, #14077:
URL: https://github.com/apache/kafka/pull/14077

   The replication offset lag is the difference of the last end offset of the 
source partition (LEO) the last replicated  source offset (LRO), +1 (to account 
for zero-based offset numbering) The offset lag is a difference (LEO-LRO), and 
its constituents are calculated at different points of time and place:
   
   LEO shall be calculated during source task's poll loop (ready to get it from 
the consumer) LRO shall be kept in an in-memory "cache", that is updated during 
the task's producer callback The difference shall be calculated when the 
freshest LEO acquired in the poll loop. The calculated amount shall be defined 
as a MirrorMaker metric.
   
   This would describe to amount of "to be replicated" number of records for a 
certain topic-partition.
   
   - Add missing test for replication-latency metric
   - Add missing test for record-byte metric
   - Add missing test for record-age metric
   - Add the metric logic to MirrorSourceTask
   - Add metric calculation &  reporting to MirrorSourceTask
   - Add tests for the new metric
   
   *More detailed description of your change,
   if necessary. The PR title and PR message become
   the squashed commit message, so use a separate
   comment to ping reviewers.*
   
   *Summary of testing strategy (including rationale)
   for the feature or bug fix. Unit and/or integration
   tests are expected for any behaviour change and
   system tests should be considered for larger changes.*
   
   ### 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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to