[
https://issues.apache.org/jira/browse/SAMZA-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15154517#comment-15154517
]
Yi Pan (Data Infrastructure) commented on SAMZA-689:
----------------------------------------------------
Hi, revisiting this one now and it seems to me that we can close as won't fix:
# We have never been able to re-produce the issue w/ correct cluster
configuration (i.e. no discrepancy between
systems.<system>.consumer.zookeeper.connect vs
systems.<system>.producer.bootstrap.servers)
# With SAMZA-864, we have a configuration to allow the job working w/
checkpoint auto-created by mistake
> 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)
>
> 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)
