You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Roman Shtykh (JIRA)" <ji...@apache.org> on 2018/08/01 04:24:00 UTC
[jira] [Commented] (IGNITE-7752) Update Ignite KafkaStreamer to use
new KafkaConsmer configuration.
[ https://issues.apache.org/jira/browse/IGNITE-7752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16564713#comment-16564713 ]
Roman Shtykh commented on IGNITE-7752:
--------------------------------------
[~amashenkov] Thank you for having a look.
* Added javadoc comments.
* Honestly, I am not aware of this (resubscribing).
The _poll_ method says {color:#629755}@throws {color}{color:#629755}org.apache.kafka.common.KafkaException for any other unrecoverable errors{color}. I don't think we can do something here, just fail (I will add an error message to log). Normally you have several brokers with _n_ replication, so having your whole Kafka cluster is a rare case.
Do you recommend to resubscribe? (Looks like it's a consumer's job)
* I can't find any infinite loop. Can you explain?
> Update Ignite KafkaStreamer to use new KafkaConsmer configuration.
> ------------------------------------------------------------------
>
> Key: IGNITE-7752
> URL: https://issues.apache.org/jira/browse/IGNITE-7752
> Project: Ignite
> Issue Type: Task
> Components: streaming
> Reporter: Andrew Mashenkov
> Assignee: Roman Shtykh
> Priority: Major
> Labels: newbie, streaming
> Fix For: 2.7
>
>
> Seems, for now it is impossible to use new style KafkaConsumer configuration in KafkaStreamer.
> The issue here is Ignite useĀ kafka.consumer.Consumer.createJavaConsumerConnector() method which creates old consumer (ZookeeperConsumerConnector).
> We should create a new KafkaConsumer instead which looks like support both, old and new style configs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)