[jira] [Commented] (KAFKA-8803) Stream will not start due to TimeoutException: Timeout expired after 60000milliseconds while awaiting InitProducerId

2019-12-09 Thread Tim Van Laer (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16991244#comment-16991244 ] Tim Van Laer commented on KAFKA-8803: - [~guozhang] Well, hard to say but to me it looked like the

[jira] [Commented] (KAFKA-8803) Stream will not start due to TimeoutException: Timeout expired after 60000milliseconds while awaiting InitProducerId

2019-11-07 Thread Tim Van Laer (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969532#comment-16969532 ] Tim Van Laer commented on KAFKA-8803: - [~bchen225242] good point, I guess so. Any way to find the

[jira] [Comment Edited] (KAFKA-8803) Stream will not start due to TimeoutException: Timeout expired after 60000milliseconds while awaiting InitProducerId

2019-11-07 Thread Tim Van Laer (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969161#comment-16969161 ] Tim Van Laer edited comment on KAFKA-8803 at 11/7/19 10:54 AM: --- I can

[jira] [Commented] (KAFKA-8803) Stream will not start due to TimeoutException: Timeout expired after 60000milliseconds while awaiting InitProducerId

2019-11-07 Thread Tim Van Laer (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969161#comment-16969161 ] Tim Van Laer commented on KAFKA-8803: - I can confirm: a rolling restart of the brokers resolved the

[jira] [Comment Edited] (KAFKA-8803) Stream will not start due to TimeoutException: Timeout expired after 60000milliseconds while awaiting InitProducerId

2019-11-07 Thread Tim Van Laer (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969090#comment-16969090 ] Tim Van Laer edited comment on KAFKA-8803 at 11/7/19 9:56 AM: -- I ran into

[jira] [Commented] (KAFKA-8803) Stream will not start due to TimeoutException: Timeout expired after 60000milliseconds while awaiting InitProducerId

2019-11-07 Thread Tim Van Laer (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969090#comment-16969090 ] Tim Van Laer commented on KAFKA-8803: - I ran into the same issue. One stream instance (the one

[jira] [Comment Edited] (KAFKA-9133) LogCleaner thread dies with: currentLog cannot be empty on an unexpected exception

2019-11-05 Thread Tim Van Laer (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-9133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16967572#comment-16967572 ] Tim Van Laer edited comment on KAFKA-9133 at 11/5/19 2:37 PM: -- [~Karolis]

[jira] [Commented] (KAFKA-9133) LogCleaner thread dies with: currentLog cannot be empty on an unexpected exception

2019-11-05 Thread Tim Van Laer (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-9133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16967572#comment-16967572 ] Tim Van Laer commented on KAFKA-9133: - [~Karolis] and i did a couple of code changes in an attempt to

[jira] [Comment Edited] (KAFKA-7447) Consumer offsets lost during leadership rebalance after bringing node back from clean shutdown

2019-10-25 Thread Tim Van Laer (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-7447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16959803#comment-16959803 ] Tim Van Laer edited comment on KAFKA-7447 at 10/25/19 2:46 PM: --- During

[jira] [Commented] (KAFKA-7447) Consumer offsets lost during leadership rebalance after bringing node back from clean shutdown

2019-10-25 Thread Tim Van Laer (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-7447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16959824#comment-16959824 ] Tim Van Laer commented on KAFKA-7447: -  Thanks [~ijuma] for looking into this, well appreciated! I 

[jira] [Comment Edited] (KAFKA-7447) Consumer offsets lost during leadership rebalance after bringing node back from clean shutdown

2019-10-25 Thread Tim Van Laer (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-7447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16959803#comment-16959803 ] Tim Van Laer edited comment on KAFKA-7447 at 10/25/19 2:45 PM: --- During

[jira] [Commented] (KAFKA-7447) Consumer offsets lost during leadership rebalance after bringing node back from clean shutdown

2019-10-25 Thread Tim Van Laer (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-7447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16959803#comment-16959803 ] Tim Van Laer commented on KAFKA-7447: - During offset loading in the recovering broker, following

[jira] [Commented] (KAFKA-7447) Consumer offsets lost during leadership rebalance after bringing node back from clean shutdown

2019-10-25 Thread Tim Van Laer (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-7447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16959789#comment-16959789 ] Tim Van Laer commented on KAFKA-7447: - Looks like we ran in a similar issue. One of our brokers lost

[jira] [Commented] (KAFKA-5998) /.checkpoint.tmp Not found exception

2019-04-10 Thread Tim Van Laer (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814356#comment-16814356 ] Tim Van Laer commented on KAFKA-5998: - Running kafka-streams 2.0.1 in Docker  {{$ cat

[jira] [Created] (KAFKA-7803) Streams internal topics config is not updated when the code is changed

2019-01-09 Thread Tim Van Laer (JIRA)
Tim Van Laer created KAFKA-7803: --- Summary: Streams internal topics config is not updated when the code is changed Key: KAFKA-7803 URL: https://issues.apache.org/jira/browse/KAFKA-7803 Project: Kafka

[jira] [Updated] (KAFKA-7803) Kafka Streams internal topics config is not updated when the code is changed

2019-01-09 Thread Tim Van Laer (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-7803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Van Laer updated KAFKA-7803: Summary: Kafka Streams internal topics config is not updated when the code is changed (was:

[jira] [Commented] (KAFKA-7290) Kafka Streams application fails to rebalance and is stuck in "Updated cluster metadata version"

2018-08-22 Thread Tim Van Laer (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-7290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16588537#comment-16588537 ] Tim Van Laer commented on KAFKA-7290: - Hi [~guozhang] and [~vvcephei],  Thanks for your time to look

[jira] [Updated] (KAFKA-7290) Kafka Streams application fails to rebalance and is stuck in "Updated cluster metadata version"

2018-08-14 Thread Tim Van Laer (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-7290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Van Laer updated KAFKA-7290: Description: Our kafka streams application crashed due to a RocksDBException, after that the

[jira] [Created] (KAFKA-7290) Kafka Streams application fails to rebalance and is stuck in "Updated cluster metadata version"

2018-08-14 Thread Tim Van Laer (JIRA)
Tim Van Laer created KAFKA-7290: --- Summary: Kafka Streams application fails to rebalance and is stuck in "Updated cluster metadata version" Key: KAFKA-7290 URL: https://issues.apache.org/jira/browse/KAFKA-7290

[jira] [Commented] (KAFKA-5998) /.checkpoint.tmp Not found exception

2018-01-30 Thread Tim Van Laer (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16344725#comment-16344725 ] Tim Van Laer commented on KAFKA-5998: - It looks like I ran into the same issue. It doesn't seem to

[jira] [Closed] (KAFKA-6248) Enable configuration of internal topics of Kafka Streams applications

2017-11-24 Thread Tim Van Laer (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Van Laer closed KAFKA-6248. --- > Enable configuration of internal topics of Kafka Streams applications >

[jira] [Resolved] (KAFKA-6248) Enable configuration of internal topics of Kafka Streams applications

2017-11-24 Thread Tim Van Laer (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Van Laer resolved KAFKA-6248. - Resolution: Not A Problem As this is supported in Kafka Streams 1.0.0, I close the stream. >

[jira] [Commented] (KAFKA-6248) Enable configuration of internal topics of Kafka Streams applications

2017-11-23 Thread Tim Van Laer (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16264106#comment-16264106 ] Tim Van Laer commented on KAFKA-6248: - Hi Bill, Thank you for the information, I must have looked

[jira] [Created] (KAFKA-6248) Enable configuration of internal topics of Kafka Streams applications

2017-11-21 Thread Tim Van Laer (JIRA)
Tim Van Laer created KAFKA-6248: --- Summary: Enable configuration of internal topics of Kafka Streams applications Key: KAFKA-6248 URL: https://issues.apache.org/jira/browse/KAFKA-6248 Project: Kafka