[
https://issues.apache.org/jira/browse/GEARPUMP-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15443656#comment-15443656
]
ASF GitHub Bot commented on GEARPUMP-197:
-----------------------------------------
Github user kkasravi commented on a diff in the pull request:
https://github.com/apache/incubator-gearpump/pull/77#discussion_r76534338
--- Diff:
external/kafka/src/main/scala/org/apache/gearpump/streaming/kafka/lib/source/consumer/FetchThread.scala
---
@@ -133,19 +133,21 @@ private[kafka] class FetchThread(
/**
* fetch message from each TopicAndPartition in a round-robin way
+ *
+ * @return whether to fetch more messages
--- End diff --
akka-streams has this GraphStage called InterLeave where upstreams are
cycled and N messages are pulled from each one. I'm wondering if we should
expose a policy related to fetch messages which is now round-robin.
> Busy loop in FetchThread when incoming queue is full
> ----------------------------------------------------
>
> Key: GEARPUMP-197
> URL: https://issues.apache.org/jira/browse/GEARPUMP-197
> Project: Apache Gearpump
> Issue Type: Bug
> Components: kafka
> Affects Versions: 0.8.1
> Reporter: Manu Zhang
> Assignee: Manu Zhang
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
