[jira] [Commented] (KAFKA-9895) Truncation request on broker start up may cause OffsetOutOfRangeException

[ https://issues.apache.org/jira/browse/KAFKA-9895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088354#comment-17088354 ] Boquan Tang commented on KAFKA-9895: [~ijuma] We've only recently upgraded from 2.2.1 to 2.4.0, we

[jira] [Created] (KAFKA-9895) Truncation request on broker start up may cause OffsetOutOfRangeException

Boquan Tang created KAFKA-9895: -- Summary: Truncation request on broker start up may cause OffsetOutOfRangeException Key: KAFKA-9895 URL: https://issues.apache.org/jira/browse/KAFKA-9895 Project: Kafka

[jira] [Commented] (KAFKA-9142) topic __transaction_state disk space grows too big

[ https://issues.apache.org/jira/browse/KAFKA-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039623#comment-17039623 ] Boquan Tang commented on KAFKA-9142: Is this the similar to

[jira] [Updated] (KAFKA-8876) KafkaBasedLog does not throw exception when some partitions of the topic is offline

[ https://issues.apache.org/jira/browse/KAFKA-8876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boquan Tang updated KAFKA-8876: --- Description: Currently KafkaBasedLog does not check if *all* partitions in the topic is online or

[jira] [Updated] (KAFKA-8876) KafkaBasedLog does not throw exception when some partitions of the topic is offline

[ https://issues.apache.org/jira/browse/KAFKA-8876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boquan Tang updated KAFKA-8876: --- Description: Currently KafkaBasedLog does not check if *all* partitions in the topic is online or

[jira] [Updated] (KAFKA-8876) KafkaBasedLog does not throw exception when some partitions of the topic is offline

[ https://issues.apache.org/jira/browse/KAFKA-8876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boquan Tang updated KAFKA-8876: --- Affects Version/s: 1.1.0 > KafkaBasedLog does not throw exception when some partitions of the topic

[jira] [Updated] (KAFKA-8876) KafkaBasedLog does not throw exception when some partitions of the topic is offline

[ https://issues.apache.org/jira/browse/KAFKA-8876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boquan Tang updated KAFKA-8876: --- Description: Currently KafkaBasedLog does not check if *all* partitions in the topic is online or

[jira] [Created] (KAFKA-8876) KafkaBasedLog does not throw exception when some partitions of the topic is offline

Boquan Tang created KAFKA-8876: -- Summary: KafkaBasedLog does not throw exception when some partitions of the topic is offline Key: KAFKA-8876 URL: https://issues.apache.org/jira/browse/KAFKA-8876

[jira] [Commented] (KAFKA-3917) Some __consumer_offsets replicas grow way too big

[ https://issues.apache.org/jira/browse/KAFKA-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905910#comment-16905910 ] Boquan Tang commented on KAFKA-3917: [~panpan.liu] This issue is solved in KAFKA-8335, you can

[jira] [Commented] (KAFKA-8335) Log cleaner skips Transactional mark and batch record, causing unlimited growth of __consumer_offsets

[ https://issues.apache.org/jira/browse/KAFKA-8335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16867181#comment-16867181 ] Boquan Tang commented on KAFKA-8335: [~francisco.juan] This patch worked for us. I have a suspicion

[jira] [Comment Edited] (KAFKA-8335) Log cleaner skips Transactional mark and batch record, causing unlimited growth of __consumer_offsets

[ https://issues.apache.org/jira/browse/KAFKA-8335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16836075#comment-16836075 ] Boquan Tang edited comment on KAFKA-8335 at 5/9/19 4:56 AM: Hi [~hachikuji]

[jira] [Commented] (KAFKA-8335) Log cleaner skips Transactional mark and batch record, causing unlimited growth of __consumer_offsets

[ https://issues.apache.org/jira/browse/KAFKA-8335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16836075#comment-16836075 ] Boquan Tang commented on KAFKA-8335: Hi [~hachikuji] thanks for replying. As Weichu commented we

[jira] [Updated] (KAFKA-8335) Log cleaner skips Transactional mark and batch record, causing unlimited growth of __consumer_offsets

[ https://issues.apache.org/jira/browse/KAFKA-8335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boquan Tang updated KAFKA-8335: --- Attachment: seg_april_25.zip > Log cleaner skips Transactional mark and batch record, causing

[jira] [Updated] (KAFKA-8335) Log cleaner skips Transactional mark and batch record, causing unlimited growth of __consumer_offsets

[ https://issues.apache.org/jira/browse/KAFKA-8335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boquan Tang updated KAFKA-8335: --- Attachment: (was: seg_april_25.zip) > Log cleaner skips Transactional mark and batch record,

[jira] [Updated] (KAFKA-8335) Log cleaner skips Transactional mark and batch record, causing unlimited growth of __consumer_offsets

[ https://issues.apache.org/jira/browse/KAFKA-8335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boquan Tang updated KAFKA-8335: --- Attachment: seg_april_25.zip > Log cleaner skips Transactional mark and batch record, causing

[jira] [Created] (KAFKA-8335) Log cleaner skips Transactional mark and batch record, causing unlimited growth of __consumer_offsets

Boquan Tang created KAFKA-8335: -- Summary: Log cleaner skips Transactional mark and batch record, causing unlimited growth of __consumer_offsets Key: KAFKA-8335 URL: https://issues.apache.org/jira/browse/KAFKA-8335

[jira] [Resolved] (KAFKA-8228) Exactly once semantics break during server restart for kafka-streams application

[ https://issues.apache.org/jira/browse/KAFKA-8228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boquan Tang resolved KAFKA-8228. Resolution: Duplicate This might duplicate KAFKA-7866, close for now and watch that ticket. >

[jira] [Commented] (KAFKA-8228) Exactly once semantics break during server restart for kafka-streams application

[ https://issues.apache.org/jira/browse/KAFKA-8228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16818492#comment-16818492 ] Boquan Tang commented on KAFKA-8228: [~mjsax] Gotcha. I'll watch that issue, if I found new evidence

[jira] [Commented] (KAFKA-8228) Exactly once semantics break during server restart for kafka-streams application

[ https://issues.apache.org/jira/browse/KAFKA-8228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16817541#comment-16817541 ] Boquan Tang commented on KAFKA-8228: Update: we did some more test, and observed that the rollback /

[jira] [Updated] (KAFKA-8228) Exactly once semantics break during server restart for kafka-streams application

[ https://issues.apache.org/jira/browse/KAFKA-8228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boquan Tang updated KAFKA-8228: --- Description: We are using 2.2.0 for kafka-streams client and 2.0.1 for server. We have a simple

[jira] [Updated] (KAFKA-8228) Exactly once semantics break during server restart for kafka-streams application

[ https://issues.apache.org/jira/browse/KAFKA-8228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boquan Tang updated KAFKA-8228: --- Description: We are using 2.2.0 for kafka-streams client and 2.0.1 for server. We have a simple

[jira] [Commented] (KAFKA-8228) Exactly once semantics break during server restart for kafka-streams application

[ https://issues.apache.org/jira/browse/KAFKA-8228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16817153#comment-16817153 ] Boquan Tang commented on KAFKA-8228: Thanks [~mjsax] for looking into this, yes I meant offsets of

[jira] [Updated] (KAFKA-8228) Exactly once semantics break during server restart for kafka-streams application

[ https://issues.apache.org/jira/browse/KAFKA-8228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boquan Tang updated KAFKA-8228: --- Description: We are using 2.2.0 for kafka-streams client and 2.0.1 for server. We have a simple

[jira] [Updated] (KAFKA-8228) Exactly once semantics break during server restart for kafka-streams application

[ https://issues.apache.org/jira/browse/KAFKA-8228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boquan Tang updated KAFKA-8228: --- Description: We are using 2.2.0 for kafka-streams client and 2.0.1 for server. We have a simple

[jira] [Updated] (KAFKA-8228) Exactly once semantics break during server restart for kafka-streams application

[ https://issues.apache.org/jira/browse/KAFKA-8228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boquan Tang updated KAFKA-8228: --- Description: We are using 2.2.0 for kafka-streams client and 2.0.1 for server. We have a simple

[jira] [Created] (KAFKA-8228) Exactly once semantics break during server restart for kafka-streams application

Boquan Tang created KAFKA-8228: -- Summary: Exactly once semantics break during server restart for kafka-streams application Key: KAFKA-8228 URL: https://issues.apache.org/jira/browse/KAFKA-8228 Project:

[jira] [Commented] (KAFKA-3917) Some __consumer_offsets replicas grow way too big

[ https://issues.apache.org/jira/browse/KAFKA-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16816874#comment-16816874 ] Boquan Tang commented on KAFKA-3917: We have met the same issue with our 2.0.1 cluster. Some