[
https://issues.apache.org/jira/browse/KAFKA-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15204620#comment-15204620
]
Dustin Cote commented on KAFKA-2670:
------------------------------------
I agree with Joel, it's probably better to keep the MirrorMaker simple.
Especially because the only way I can actually see to do this is to add another
branch statement into the hot code path for processing events, which marginally
slows the MirrorMaker. I'm going to checkout that interceptor API in some more
detail and maybe it makes sense to add an example that would accomplish this
same thing. For example, intercept every X number of events and /dev/null them
instead of letting them make it to the target cluster. When I have a better
handle on that I will make a pull request.
> add sampling rate to MirrorMaker
> --------------------------------
>
> Key: KAFKA-2670
> URL: https://issues.apache.org/jira/browse/KAFKA-2670
> Project: Kafka
> Issue Type: Wish
> Components: tools
> Reporter: Christian Tramnitz
> Priority: Minor
>
> MirrorMaker could be used to copy data to different Kafka instances in
> different environments (i.e. from production to development or test), but
> often these are not at the same scale as production. A sampling rate could be
> introduced to MirrorMaker to define a ratio of data to copied (per topic) to
> downstream instances. Of course this should be 1:1 (or 100%) per default.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
