[
https://issues.apache.org/jira/browse/KAFKA-7593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677704#comment-16677704
]
Oleg Kuznetsov edited comment on KAFKA-7593 at 11/7/18 5:27 AM:
----------------------------------------------------------------
[~rhauch] Sure, the workaround is clear, but the ticket is more about letting
user heads up about the problem preventively.
For instance, by throwing an exception.
Is it possible to have feedback from the broker that this payload is too big
and just stop working?
was (Author: olkuznsmith):
[~rhauch] Sure, workaround is clear, but the ticket is more about letting user
heads up about the problem preventively.
For instance, by throwing exception.
Is it possible to have feedback from broker that this payload is too big and
just stop working?
> Infinite restart loop when failed to store big config for task
> --------------------------------------------------------------
>
> Key: KAFKA-7593
> URL: https://issues.apache.org/jira/browse/KAFKA-7593
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Affects Versions: 1.1.0
> Reporter: Oleg Kuznetsov
> Priority: Major
>
> In case when config message for config topic is greater than kafka broker
> allows to store, source connector starts infinite restart loop without any
> error indication.
> There could be an exception thrown in this case or a smarter handling of big
> config.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
