[
https://issues.apache.org/jira/browse/KAFKA-4937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949081#comment-15949081
]
ASF GitHub Bot commented on KAFKA-4937:
---------------------------------------
GitHub user dguy opened a pull request:
https://github.com/apache/kafka/pull/2769
KAFKA-4937: Batch resetting offsets in Streams' StoreChangelogReader
change `consumer.position` so that it always updates any partitions that
need an update. Keep track of partitions that `seekToBeginning` in
`StoreChangeLogReader` and do the `consumer.position` call after all
`seekToBeginning` calls.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dguy/kafka kafka-4937
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2769.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2769
----
commit 9c4306040a1b6802de9dad84351477f4f3145c74
Author: Damian Guy <damian....@gmail.com>
Date: 2017-03-30T13:38:34Z
batch fetch of consumer positions
----
> Batch resetting offsets in Streams' StoreChangelogReader
> --------------------------------------------------------
>
> Key: KAFKA-4937
> URL: https://issues.apache.org/jira/browse/KAFKA-4937
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Reporter: Guozhang Wang
> Assignee: Damian Guy
> Labels: newbie++, performance
>
> Currently in {{StoreChangelogReader}} we are calling {{consumer.position()}}
> when logging as well as setting starting offset right after
> {{seekingToBeginning}}, which will incur a blocking round trip with offset
> request. We should consider batching those in a single round trip for all
> partitions that needs to seek to beginning (i.e. needs to reset offset).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
