[
https://issues.apache.org/jira/browse/KAFKA-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14306332#comment-14306332
]
Jay Kreps commented on KAFKA-1760:
----------------------------------
Actually shameful to say but I'm not sure this is a bug but rather a "feature".
We need to give the client it's own connection to the co-ordinator, but the
existing client maintains a single connection per node id. My hack for this is
to give the coordinator connection the node id -MAX_INT:
{code}
if (response.errorCode() == Errors.NONE.code())
return new Node(Integer.MIN_VALUE, response.node().host(),
response.node().port());
{code}
I would agree this is somewhat egregious, but I really am not sure about how we
would change the client to model connections and nodes differently for a
non-hack to work and still be usable.
> Implement new consumer client
> -----------------------------
>
> Key: KAFKA-1760
> URL: https://issues.apache.org/jira/browse/KAFKA-1760
> Project: Kafka
> Issue Type: Sub-task
> Components: consumer
> Reporter: Jay Kreps
> Assignee: Jay Kreps
> Fix For: 0.8.3
>
> Attachments: KAFKA-1760.patch, KAFKA-1760_2015-01-11_16:57:15.patch,
> KAFKA-1760_2015-01-18_19:10:13.patch, KAFKA-1760_2015-01-21_08:42:20.patch,
> KAFKA-1760_2015-01-22_10:03:26.patch, KAFKA-1760_2015-01-22_20:21:56.patch,
> KAFKA-1760_2015-01-23_13:13:00.patch, KAFKA-1760_2015-01-29_03:20:20.patch
>
>
> Implement a consumer client.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
