Re: [DISCUSS] KIP-263: Allow broker to skip sanity check of inactive segments on broker startup

Hey Colin, It seems that when broker recovers a segment, all snapshots after this segment will be deleted. It means that the active segment can not be used for transaction related operation if a non-active segment needs to be recovered. Thus the suggested approach may not be safe if users need to

Jenkins build is back to normal : kafka-trunk-jdk8 #2449

See

Re: [DISCUSS] KIP-253: Support in-order message delivery with partition expansion

Hey Jan, In the current proposal, the consumer will be blocked on waiting for other consumers of the group to consume up to a given offset. In most cases, all consumers should be close to the LEO of the partitions when the partition expansion happens. Thus the time waiting should not be long e.g.

Re: [DISCUSS] KIP-253: Support in-order message delivery with partition expansion

Hey Jay, Allen, Jason, Jun, Thanks much for the valuable feedback. It is very good point that we can reduce the state that needs to be stored/loaded by using linear hashing. I have updated the KIP to use linear hashing as suggested. The benefits of using linear hashing is summarized in "Changes in

Jenkins build is back to normal : kafka-trunk-jdk9 #445

See

Re: [VOTE] KIP-171 - Extend Consumer Group Reset Offset for Stream Application

I agree. --execute is inconsistent with the way UNIX commands normally work. Normally, if you don't want something to be executed, you pass something like a --dry-run flag. Users expect a command to be run when the run it... that's the reason why this has created so much confusion for Kafka us

[jira] [Resolved] (KAFKA-6606) Regression in consumer auto-commit backoff behavior

[ https://issues.apache.org/jira/browse/KAFKA-6606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6606. Resolution: Fixed Note this issue did not affect any released version. > Regression in cons

[jira] [Created] (KAFKA-6609) Offset commit reordering possible on coordinator disconnect

Jason Gustafson created KAFKA-6609: -- Summary: Offset commit reordering possible on coordinator disconnect Key: KAFKA-6609 URL: https://issues.apache.org/jira/browse/KAFKA-6609 Project: Kafka

[jira] [Created] (KAFKA-6608) Add timeout parameter to methods which fetches and resets offsets

Richard Yu created KAFKA-6608: - Summary: Add timeout parameter to methods which fetches and resets offsets Key: KAFKA-6608 URL: https://issues.apache.org/jira/browse/KAFKA-6608 Project: Kafka Is