ion
> message.max.bytes, which may cause the coordinator broker to allocate too
> much memory and cause OOM
> -
>
>
issues.
Thanks,
Thanks,
On Sun, 16 Jun 2019 at 11:39, 王双双 wrote:
> Hello everyone,
> I have recently encountered a problem with the parameter
> 'message.max.bytes'. Here are the details: There are 1000 messages that I
> have not consumed, each message is 7KB, and a log
Hello everyone,
I have recently encountered a problem with the parameter 'message.max.bytes'.
Here are the details: There are 1000 messages that I have not consumed, each
message is 7KB, and a log under
the topic is 106MB. I altered the parameter 'message.max.bytes' from
Sriharsha Chintalapani created KAFKA-1844:
-
Summary: Topic message.max.bytes can be larger than the
replica.fetch.max.bytes
Key: KAFKA-1844
URL: https://issues.apache.org/jira/browse/KAFKA-1844
llow customizing max.message.size
per topic. Such customization may break downstream consumers like MirrorMaker.
I am not sure if there is a strong use case for the per topic customization.
> Brokers should make sure replica.fetch.max.bytes >= message
nrao] Any thoughts on proposed approach adding an api to
return broker config
> Brokers should make sure replica.fetch.max.bytes >= message.max.bytes
> -
>
> Key: KAFKA-1273
>
. We can probably just
create a new jira.
> Brokers should make sure replica.fetch.max.bytes >= message.max.bytes
> -
>
> Key: KAFKA-1273
> URL: https://issues.apache.org/
e as well. [~junrao], are you able to?
> Brokers should make sure replica.fetch.max.bytes >= message.max.bytes
> -
>
> Key: KAFKA-1273
> URL: https://issues.apache.org/jira/browse/KAFKA
option is to add an api that return a configResponse which contains all the
server.properties that user defined along with defaults. Please let me know
what you think about these approaches.
> Brokers should make sure replica.fetch.max
s. I am able to reproduce this . [~nehanarkhede] I don't
think I've permissions to re-open the JIRA. Could you please re-open , I'll
send a patch. Thanks.
> Brokers should make sure replica.fetch.max.byte
Yes. working on reproducing it.
> Brokers should make sure replica.fetch.max.bytes >= message.max.bytes
> -
>
> Key: KAFKA-1273
> URL: https://issues.apache.org/jira/browse/KAFKA-1273
tes >= message.max.bytes
> -
>
> Key: KAFKA-1273
> URL: https://issues.apache.org/jira/browse/KAFKA-1273
> Project: Kafka
> Issue Type: Bug
> Component
you override message.max.bytes in the config file it complains on
startup, but Kafka allows you to modify this value per-topic.
I have a topic with a higher value of message.max.bytes, and it was very
difficult to diagnose why its replicas could not stay in sync.
> Brokers should ma
[
https://issues.apache.org/jira/browse/KAFKA-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede closed KAFKA-1273.
> Brokers should make sure replica.fetch.max.bytes >= message.max
duce this in the trunk as kafka-server-start.sh fails to
start the broker throwing
java.lang.IllegalArgumentException: requirement failed: replica.fetch.max.bytes
has value 1024 which is not in the range (2048,2147483647).
its checking if the replica.fetch.max.bytes >= message.max.bytes.
&g
[
https://issues.apache.org/jira/browse/KAFKA-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1273:
---
Labels: newbie (was: )
> Brokers should make sure replica.fetch.max.bytes >= message.max
Dong Zhong created KAFKA-1273:
-
Summary: Brokers should make sure replica.fetch.max.bytes >=
message.max.bytes
Key: KAFKA-1273
URL: https://issues.apache.org/jira/browse/KAFKA-1273
Project: Ka
)
> Enforce that the value for replica.fetch.max.bytes is always >= the value for
> message.max.bytes
> ---
>
> Key: KAFKA-995
> URL: https://issues.apache.
ue for
> message.max.bytes
> ---
>
> Key: KAFKA-995
> URL: https://issues.apache.org/jira/browse/KAFKA-995
> Project: Kafka
>
hat the value for replica.fetch.max.bytes is always >= the value for
> message.max.bytes
> ---
>
> Key: KAFKA-995
> URL: https://issues.apache.
ue for
> message.max.bytes
> ---
>
> Key: KAFKA-995
> URL: https://issues.apache.org/jira/browse/KAFKA-995
> Project: Kafka
>
is always >= the value for
> message.max.bytes
> ---
>
> Key: KAFKA-995
> URL: https://issues.apache.org/jira/browse/KAFKA-995
> Project: Kaf
ays >= the value for
> message.max.bytes
> ---
>
> Key: KAFKA-995
> URL: https://issues.apache.org/jira/browse/KAFKA-995
> Project: Kaf
Sam Meder created KAFKA-995:
---
Summary: Enforce that the value for replica.fetch.max.bytes is
always >= the value for message.max.bytes
Key: KAFKA-995
URL: https://issues.apache.org/jira/browse/KAFKA-
24 matches
Mail list logo
