[
https://issues.apache.org/jira/browse/KAFKA-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15868433#comment-15868433
]
Jun Rao commented on KAFKA-4340:
--------------------------------
[~becket_qin], after committing the patch in this jira. One of our system tests
start to fail consistently:
https://testbreak.confluent.io/kiosk/test_result?id=15685
In the failed tests, we use 0.9.0.1 producer to publish to trunk brokers and
the producer keeps getting the following error.
{code}
[2017-02-15 10:10:17,275] INFO Kafka version : 0.9.0.1
(org.apache.kafka.common.utils.AppInfoParser)
[2017-02-15 10:10:17,276] INFO Kafka commitId : 23c69d62a0cabf06
(org.apache.kafka.common.utils.AppInfoParser)
[2017-02-15 10:10:17,467] WARN Unexpected error code: 32.
(org.apache.kafka.common.protocol.Errors)
[2017-02-15 10:10:17,697] WARN Unexpected error code: 32.
(org.apache.kafka.common.protocol.Errors)
[2017-02-15 10:10:17,730] WARN Unexpected error code: 32.
(org.apache.kafka.common.protocol.Errors)
[2017-02-15 10:10:17,735] WARN Unexpected error code: 32.
(org.apache.kafka.common.protocol.Errors)
[2017-02-15 10:10:17,739] WARN Unexpected error code: 32.
(org.apache.kafka.common.protocol.Errors)
[2017-02-15 10:10:17,744] WARN Unexpected error code: 32.
(org.apache.kafka.common.protocol.Errors)
[2017-02-15 10:10:18,108] WARN Unexpected error code: 32.
(org.apache.kafka.common.protocol.Errors)
[2017-02-15 10:10:18,123] WARN Unexpected error code: 32.
(org.apache.kafka.common.protocol.Errors)
[2017-02-15 10:10:18,126] WARN Unexpected error code: 32.
(org.apache.kafka.common.protocol.Errors)
[2017-02-15 10:10:18,128] WARN Unexpected error code: 32.
(org.apache.kafka.common.protocol.Errors)
[2017-02-15 10:10:18,130] WARN Unexpected error code: 32.
(org.apache.kafka.common.protocol.Errors)
[2017-02-15 10:10:18,295] INFO Closing the Kafka producer with timeoutMillis =
9223372036854775807 ms. (org.apache.kafka.clients.producer.KafkaProducer)
[2017-02-15 10:10:18,319] WARN Unexpected error code: 32.
(org.apache.kafka.common.protocol.Errors)
[2017-02-15 10:10:18,325] WARN Unexpected error code: 32.
(org.apache.kafka.common.protocol.Errors)
[2017-02-15 10:10:18,327] WARN Unexpected error code: 32.
(org.apache.kafka.common.protocol.Errors)
[2017-02-15 10:10:18,328] WARN Unexpected error code: 32.
(org.apache.kafka.common.protocol.Errors)
[2017-02-15 10:10:18,329] WARN Unexpected error code: 32.
(org.apache.kafka.common.protocol.Errors)
{code}
It seems that the issue is that messages from the 0.9 producer will get the
default -1 timestamp and will be rejected by the new default
message.timestamp.difference.max.ms. For backward compatibility, perhaps we
should not reject messages with -1 timestamp?
> Change the default value of log.message.timestamp.difference.max.ms to the
> same as log.retention.ms
> ---------------------------------------------------------------------------------------------------
>
> Key: KAFKA-4340
> URL: https://issues.apache.org/jira/browse/KAFKA-4340
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.10.1.0
> Reporter: Jiangjie Qin
> Assignee: Jiangjie Qin
> Fix For: 0.10.3.0
>
>
> [~junrao] brought up the following scenario:
> If users are pumping data with timestamp already passed log.retention.ms into
> Kafka, the messages will be appended to the log but will be immediately
> rolled out by log retention thread when it kicks in and the messages will be
> deleted.
> To avoid this produce-and-deleted scenario, we can set the default value of
> log.message.timestamp.difference.max.ms to be the same as log.retention.ms.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
