[
https://issues.apache.org/jira/browse/SAMZA-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14619459#comment-14619459
]
Chinmay Soman commented on SAMZA-689:
-------------------------------------
I see the exception in the AM log.
> When Kafka has topic auto-creation turned on, checkpoint topics may be
> created w/ wrong partition numbers
> ---------------------------------------------------------------------------------------------------------
>
> Key: SAMZA-689
> URL: https://issues.apache.org/jira/browse/SAMZA-689
> Project: Samza
> Issue Type: Bug
> Components: container
> Affects Versions: 0.9.1
> Reporter: Yi Pan (Data Infrastructure)
> Fix For: 0.9.1
>
>
> When Kafka topic auto-creation is turned on in the brokers, a fetch metadata
> API call will result in topic auto-creation w/ default number of partitions.
> In Samza code, we should always try to create the checkpoint/changelog topic
> w/ the expected number of partitions first, then call fetch metadata to avoid
> topic auto-creation creating the topic w/ un-wanted number of partitions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
