[
https://issues.apache.org/jira/browse/KAFKA-6248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edmondo Porcu updated KAFKA-6248:
---------------------------------
Comment: was deleted
(was: Does it work for max.request.size?
-Dtopic.max.request.size=3000000 -Dproducer.max.request.size=3000000
Exception in thread
"analysis-input-enricher-e1c4502d-62e9-43a6-bf59-b37dcfc77ce2-StreamThread-1"
org.apache.kafka.streams.errors.StreamsException: task [1_0] Abort sending
since an error caught with a previous record (key NON PREVISTO value
[B@62851189 timestamp 1555104485966) to topic
analysis-input-enricher-cr-STATE-STORE-0000000001-changelog due to
org.apache.kafka.common.errors.RecordTooLargeException: The message is 1403267
bytes when serialized which is larger than the maximum request size you have
configured with the max.request.size configuration.)
> Enable configuration of internal topics of Kafka Streams applications
> ---------------------------------------------------------------------
>
> Key: KAFKA-6248
> URL: https://issues.apache.org/jira/browse/KAFKA-6248
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Tim Van Laer
> Priority: Minor
>
> In the current implementation of Kafka Streams, it is not possible to set
> custom configuration to internal topics (e.g. max.message.bytes,
> retention.ms...). It would be nice if a developer can set some specific
> configuration.
> E.g. if you want to store messages bigger than 1MiB in a state store, you
> have to alter the corresponding changelog topic with a max.message.bytes
> setting.
> The workaround is to create the 'internal' topics upfront using the correct
> naming convention so Kafka Streams will use the explicitly defined topics as
> if they are internal.
> An alternative is to alter the internal topics after the Kafka Streams
> application is started and has created its internal topics.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
