[
https://issues.apache.org/jira/browse/KAFKA-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dustin Cote resolved KAFKA-3993.
--------------------------------
Resolution: Duplicate
Marking this a duplicate of KAFKA-3129. The workaround here is to set acks=1
on the console producer but acks=0 shouldn't mean that all requests don't get
to make it out of the queue before close() finishes. I'll follow up on
KAFKA-3129 to keep everything in one place.
> Console producer drops data
> ---------------------------
>
> Key: KAFKA-3993
> URL: https://issues.apache.org/jira/browse/KAFKA-3993
> Project: Kafka
> Issue Type: Bug
> Components: clients
> Affects Versions: 0.10.0.0
> Reporter: Roger Hoover
>
> The console producer drops data when if the process exits too quickly. I
> suspect that the shutdown hook does not call close() or something goes wrong
> during that close().
> Here's a simple to illustrate the issue:
> {noformat}
> export BOOTSTRAP_SERVERS=localhost:9092
> export TOPIC=bar
> export MESSAGES=10000
> ./bin/kafka-topics.sh --zookeeper localhost:2181 --create --partitions 1
> --replication-factor 1 --topic "$TOPIC" \
> && echo "acks=all" > /tmp/producer.config \
> && echo "linger.ms=0" >> /tmp/producer.config \
> && seq "$MESSAGES" | ./bin/kafka-console-producer.sh --broker-list
> "$BOOTSTRAP_SERVERS" --topic "$TOPIC" --producer-config /tmp/producer.config \
> && ./bin/kafka-console-consumer.sh --bootstrap-server "$BOOTSTRAP_SERVERS"
> --new-consumer --from-beginning --max-messages "${MESSAGES}" --topic "$TOPIC"
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
