[
https://issues.apache.org/jira/browse/KAFKA-8813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Cheng updated KAFKA-8813:
-------------------------------
Description:
In Partition.createLog we do:
{{val config = LogConfig.fromProps(logManager.currentDefaultConfig.originals,
props)
val log = logManager.getOrCreateLog(topicPartition, config, isNew,
isFutureReplica)}}
Config changes that arrive after configs are loaded from ZK, but before
LogManager added the partition to `futureLogs` or `currentLogs` where the
dynamic config handlers picks up topics to update their configs, will be lost.
was:
In Partition.createLog we do:
{{val config = LogConfig.fromProps(logManager.currentDefaultConfig.originals,
props)val log = logManager.getOrCreateLog(topicPartition, config, isNew,
isFutureReplica)}}
Config changes that arrive after configs are loaded from ZK, but before
LogManager added the partition to `futureLogs` or `currentLogs` where the
dynamic config handlers picks up topics to update their configs, will be lost.
> Race condition when creating topics and changing their configuration
> --------------------------------------------------------------------
>
> Key: KAFKA-8813
> URL: https://issues.apache.org/jira/browse/KAFKA-8813
> Project: Kafka
> Issue Type: Bug
> Reporter: Gwen Shapira
> Priority: Major
>
> In Partition.createLog we do:
> {{val config = LogConfig.fromProps(logManager.currentDefaultConfig.originals,
> props)
> val log = logManager.getOrCreateLog(topicPartition, config, isNew,
> isFutureReplica)}}
> Config changes that arrive after configs are loaded from ZK, but before
> LogManager added the partition to `futureLogs` or `currentLogs` where the
> dynamic config handlers picks up topics to update their configs, will be lost.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
