kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manikumar (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (KAFKA-623) It should be possible to re-create KafkaStreams after an exception, without recreating ConsumerConnector
Date Sun, 29 Oct 2017 09:31:00 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Manikumar resolved KAFKA-623.
-----------------------------
    Resolution: Auto Closed

Closing inactive issue. The old consumer is no longer supported.

> It should be possible to re-create KafkaStreams after an exception, without recreating
ConsumerConnector
> --------------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-623
>                 URL: https://issues.apache.org/jira/browse/KAFKA-623
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.8.0
>            Reporter: Jason Rosenberg
>
> This issue came out of a discussion on the user mailing list (not something I experienced
directly).
> Bob Cotton reported:
> "During the implementation of a custom Encoder/Decoder we noticed that
> should the Decoder throw an exception, the KafkaStream that it is in use
> becomes invalid.
> Searching the mailing list indicates that the only way to recover from an
> invalid stream is to shutdown the whole high-level consumer and restart.
> Is there a better way to recover from this?
> Thanks for the responsiveness on the mailing list."
> ......
> And then Neha responded:
> "This is a bug. Ideally, we should allow restarting the consumer
> streams when they encounter an error.
> Can you file a JIRA ?
> Thanks,
> Neha"
> Jason



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message