Re: Please Help with Error: org.apache.kafka.common.network.InvalidReceiveException: Invalid receive (size = ...

Hi Roger, It looks like you need to update your broker configuration to include a higher value for message.max.bytes. Hth, Malcolm McFarland Cavulus This correspondence is from HealthPlanCRM, LLC, d/b/a Cavulus. Any unauthorized or improper disclosure, copying, distribution, or use of the

Re: [DISCUSS] KIP-759: Unneeded repartition canceling

Hey Ivan I completely agree that adding it as a config to Grouped/Joined/etc isn't much better, I was just listing it for completeness, and that I would prefer to make it a configuration of the key-changing operation itself -- that's what I meant by a better alternative might be to introduce

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.0 #87

See

Please Help with Error: org.apache.kafka.common.network.InvalidReceiveException: Invalid receive (size = ...

Hi, We have received the following error (running kafka v2.3.0): org.apache.kafka.common.network.InvalidReceiveException: Invalid receive (size = 1195725856 larger than 1048576000) I've attached our configuration/properties, hope it helps. Here are the details:

Re: [DISCUSS] KIP-655: Windowed "Distinct" Operation for KStream

> - Why restrict de-duplication for the key only? Should we not also > consider the value (or make it somehow flexible and let the user choose?) Wasn't it the first idea that we abandoned (I mean, to provide 'KeyExtractor' and so on)? In order to keep things simple we decided to make

Re: [DISCUSS] KIP-759: Unneeded repartition canceling

Hi Matthias, Concerning the naming: I like `markAsPartitioned`, because it describes what this operation is actually doing! Hi Sophie, I see the concern about poor code cohesion. We declare key mapping in one place of code, then later in another place we say "markAsPartitioned()". When we

[jira] [Created] (KAFKA-13175) The state for creating a topic is marked deep, but indicates that the topic already exists.

yangshengwei created KAFKA-13175: Summary: The state for creating a topic is marked deep, but indicates that the topic already exists. Key: KAFKA-13175 URL: https://issues.apache.org/jira/browse/KAFKA-13175

Jenkins build is unstable: Kafka » Kafka Branch Builder » trunk #397

See

[jira] [Reopened] (KAFKA-13128) Flaky Test StoreQueryIntegrationTest.shouldQueryStoresAfterAddingAndRemovingStreamThread

[ https://issues.apache.org/jira/browse/KAFKA-13128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman reopened KAFKA-13128: Assignee: (was: A. Sophie Blee-Goldman) Failed again for a