kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manikumar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-4788) Broker level configuration 'log.segment.bytes' not used when 'segment.bytes' not configured per topic.
Date Thu, 23 Feb 2017 11:30:44 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-4788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880281#comment-15880281

Manikumar commented on KAFKA-4788:

looks like KAFKA-4092 change introduced this issue.  During validation, we are not inlcuding
original/broker props. 

> Broker level configuration 'log.segment.bytes' not used when 'segment.bytes' not configured
per topic.
> ------------------------------------------------------------------------------------------------------
>                 Key: KAFKA-4788
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4788
>             Project: Kafka
>          Issue Type: Bug
>          Components: log
>    Affects Versions:
>            Reporter: Ciprian Pascu
> In the previous version, if there was not topic level configuration 'segment.bytes',
then the corresponding value from the broker configuration was used (for 'segment.bytes',
this is the value configured for 'log.segment.bytes'); in, if the configuration at
topic level is missing, then the value configured at broker level is not used, some kind of
default value for that broker level configuration is used (for 'log.retention.bytes', this
is 'val LogSegmentBytes = 1 * 1024 * 1024 * 1024').
> However, in the documentation it is said: 'A given server default config value only applies
to a topic if it does not have an explicit topic config override.'; so, according to this,
if there is, for example, no value configured for 'segment.bytes', then the value configured
for 'log.segment.bytes' should be used.

This message was sent by Atlassian JIRA

View raw message