[jira] [Commented] (KAFKA-1194) The kafka broker cannot delete the old log files after the configured time

[ https://issues.apache.org/jira/browse/KAFKA-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16463443#comment-16463443 ] Christoph Schmidt commented on KAFKA-1194: -- Would love to have this upgraded to B

[jira] [Commented] (KAFKA-6188) Broker fails with FATAL Shutdown - log dirs have failed

[ https://issues.apache.org/jira/browse/KAFKA-6188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16463436#comment-16463436 ] Christoph Schmidt commented on KAFKA-6188: -- Added link to KAFKA-1194, which appea

[jira] [Commented] (KAFKA-6857) LeaderEpochFileCache.endOffsetFor() should check for UNDEFINED_EPOCH explicitly

[ https://issues.apache.org/jira/browse/KAFKA-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16463400#comment-16463400 ] ASF GitHub Bot commented on KAFKA-6857: --- hachikuji closed pull request #4967: KAFKA-

[jira] [Commented] (KAFKA-6861) Missing ')' in Kafka Streams documentation

[ https://issues.apache.org/jira/browse/KAFKA-6861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16463397#comment-16463397 ] ASF GitHub Bot commented on KAFKA-6861: --- zer0Id0l opened a new pull request #139: [K

[jira] [Created] (KAFKA-6861) Missing ')' in Kafka Streams documentation

Ravi Raj Singh created KAFKA-6861: - Summary: Missing ')' in Kafka Streams documentation Key: KAFKA-6861 URL: https://issues.apache.org/jira/browse/KAFKA-6861 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-6860) NPE when reinitializeStateStores with eos enabled

[ https://issues.apache.org/jira/browse/KAFKA-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ko byoung kwon updated KAFKA-6860: -- Description: *Symptom* With EOS enabled , Reinitializing stateStores get an NPE because checkpo

[jira] [Updated] (KAFKA-6860) NPE when reinitializeStateStores with eos enabled

[ https://issues.apache.org/jira/browse/KAFKA-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ko byoung kwon updated KAFKA-6860: -- Description: *Symptom* With EOS enabled , Reinitializing stateStores get an NPE because checkpo

[jira] [Updated] (KAFKA-6860) NPE when reinitializeStateStores with eos enabled(true)

[ https://issues.apache.org/jira/browse/KAFKA-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ko byoung kwon updated KAFKA-6860: -- Summary: NPE when reinitializeStateStores with eos enabled(true) (was: missing creating checkpo

[jira] [Updated] (KAFKA-6860) NPE when reinitializeStateStores with eos enabled

[ https://issues.apache.org/jira/browse/KAFKA-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ko byoung kwon updated KAFKA-6860: -- Description: *Symptom* With EOS enabled , Reinitializing stateStores get an NPE because checkpo

[jira] [Updated] (KAFKA-6860) NPE when reinitializeStateStores with eos enabled

[ https://issues.apache.org/jira/browse/KAFKA-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ko byoung kwon updated KAFKA-6860: -- Summary: NPE when reinitializeStateStores with eos enabled (was: NPE when reinitializeStateStor

[jira] [Updated] (KAFKA-6860) missing creating checkpoint when reinitializeStateStores with eosEnabled(true)

[ https://issues.apache.org/jira/browse/KAFKA-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ko byoung kwon updated KAFKA-6860: -- Description: First of all, please understand that my English is not fluent. *Symptom* With EOS

[jira] [Created] (KAFKA-6860) missing creating checkpoint when reinitializeStateStores with eosEnabled(true)

ko byoung kwon created KAFKA-6860: - Summary: missing creating checkpoint when reinitializeStateStores with eosEnabled(true) Key: KAFKA-6860 URL: https://issues.apache.org/jira/browse/KAFKA-6860 Projec

[jira] [Commented] (KAFKA-6840) support windowing in ktable API

[ https://issues.apache.org/jira/browse/KAFKA-6840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16463304#comment-16463304 ] Boyang Chen commented on KAFKA-6840: I think alternatively we could extend class `Mate

[jira] [Commented] (KAFKA-6840) support windowing in ktable API

[ https://issues.apache.org/jira/browse/KAFKA-6840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16463297#comment-16463297 ] Boyang Chen commented on KAFKA-6840: [~mjsax] Sorry haven't updated this thread for a

[jira] [Created] (KAFKA-6859) Follower should not send OffsetForLeaderEpoch for undefined leader epochs

Anna Povzner created KAFKA-6859: --- Summary: Follower should not send OffsetForLeaderEpoch for undefined leader epochs Key: KAFKA-6859 URL: https://issues.apache.org/jira/browse/KAFKA-6859 Project: Kafka

[jira] [Assigned] (KAFKA-6858) Log.truncateTo() may truncate to an earlier offset than requested

[ https://issues.apache.org/jira/browse/KAFKA-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Povzner reassigned KAFKA-6858: --- Assignee: Anna Povzner > Log.truncateTo() may truncate to an earlier offset than requested >

[jira] [Commented] (KAFKA-6857) LeaderEpochFileCache.endOffsetFor() should check for UNDEFINED_EPOCH explicitly

[ https://issues.apache.org/jira/browse/KAFKA-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16463224#comment-16463224 ] ASF GitHub Bot commented on KAFKA-6857: --- apovzner opened a new pull request #4967: K

[jira] [Assigned] (KAFKA-6857) LeaderEpochFileCache.endOffsetFor() should check for UNDEFINED_EPOCH explicitly

[ https://issues.apache.org/jira/browse/KAFKA-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Povzner reassigned KAFKA-6857: --- Assignee: Anna Povzner > LeaderEpochFileCache.endOffsetFor() should check for UNDEFINED_EPOCH

[jira] [Created] (KAFKA-6858) Log.truncateTo() may truncate to an earlier offset than requested

Jun Rao created KAFKA-6858: -- Summary: Log.truncateTo() may truncate to an earlier offset than requested Key: KAFKA-6858 URL: https://issues.apache.org/jira/browse/KAFKA-6858 Project: Kafka Issue Ty

[jira] [Created] (KAFKA-6857) LeaderEpochFileCache.endOffsetFor() should check for UNDEFINED_EPOCH explicitly

Jun Rao created KAFKA-6857: -- Summary: LeaderEpochFileCache.endOffsetFor() should check for UNDEFINED_EPOCH explicitly Key: KAFKA-6857 URL: https://issues.apache.org/jira/browse/KAFKA-6857 Project: Kafka

[jira] [Resolved] (KAFKA-6854) Log cleaner fails with transaction markers that are deleted during clean

[ https://issues.apache.org/jira/browse/KAFKA-6854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6854. Resolution: Fixed > Log cleaner fails with transaction markers that are deleted during clean

[jira] [Commented] (KAFKA-6854) Log cleaner fails with transaction markers that are deleted during clean

[ https://issues.apache.org/jira/browse/KAFKA-6854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462992#comment-16462992 ] ASF GitHub Bot commented on KAFKA-6854: --- hachikuji closed pull request #4962: KAFKA-

[jira] [Comment Edited] (KAFKA-5716) Connect: When SourceTask.commit it is possible not everthing from SourceTask.poll has been sent

[ https://issues.apache.org/jira/browse/KAFKA-5716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462890#comment-16462890 ] Randall Hauch edited comment on KAFKA-5716 at 5/3/18 6:41 PM: --

[jira] [Commented] (KAFKA-5716) Connect: When SourceTask.commit it is possible not everthing from SourceTask.poll has been sent

[ https://issues.apache.org/jira/browse/KAFKA-5716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462890#comment-16462890 ] Randall Hauch commented on KAFKA-5716: -- [~steff1193], thanks for all the work on this

[jira] [Created] (KAFKA-6856) Consumer Group hung in initialization/bad state

Todd created KAFKA-6856: --- Summary: Consumer Group hung in initialization/bad state Key: KAFKA-6856 URL: https://issues.apache.org/jira/browse/KAFKA-6856 Project: Kafka Issue Type: Bug Repor

[jira] [Updated] (KAFKA-6853) ResponseMetadata calculates latency incorrectly (and therefore ZooKeeperRequestLatencyMs is incorrect)

[ https://issues.apache.org/jira/browse/KAFKA-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-6853: --- Fix Version/s: 1.1.1 2.0.0 > ResponseMetadata calculates latency incorrectly (and t

[jira] [Resolved] (KAFKA-6853) ResponseMetadata calculates latency incorrectly (and therefore ZooKeeperRequestLatencyMs is incorrect)

[ https://issues.apache.org/jira/browse/KAFKA-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6853. Resolution: Fixed > ResponseMetadata calculates latency incorrectly (and therefore > ZooKeeperReque

[jira] [Commented] (KAFKA-6853) ResponseMetadata calculates latency incorrectly (and therefore ZooKeeperRequestLatencyMs is incorrect)

[ https://issues.apache.org/jira/browse/KAFKA-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462760#comment-16462760 ] ASF GitHub Bot commented on KAFKA-6853: --- ijuma closed pull request #4961: KAFKA-6853

[jira] [Updated] (KAFKA-6855) Kafka fails to start with Java 10 due to faulty Java version detection

[ https://issues.apache.org/jira/browse/KAFKA-6855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-6855: --- Summary: Kafka fails to start with Java 10 due to faulty Java version detection (was: Kafka fails to

[jira] [Resolved] (KAFKA-6855) Kafka fails to start due to faulty Java version detection

[ https://issues.apache.org/jira/browse/KAFKA-6855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6855. Resolution: Fixed Fix Version/s: 1.1.1 2.0.0 Thanks for the report. This h

[jira] [Assigned] (KAFKA-6855) Kafka fails to start due to faulty Java version detection

[ https://issues.apache.org/jira/browse/KAFKA-6855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-6855: -- Assignee: Ismael Juma > Kafka fails to start due to faulty Java version detection > ---

[jira] [Commented] (KAFKA-6854) Log cleaner fails with transaction markers that are deleted during clean

[ https://issues.apache.org/jira/browse/KAFKA-6854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462695#comment-16462695 ] ASF GitHub Bot commented on KAFKA-6854: --- rajinisivaram opened a new pull request #49

[jira] [Updated] (KAFKA-6854) Log cleaner fails with transaction markers that are deleted during clean

[ https://issues.apache.org/jira/browse/KAFKA-6854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-6854: -- Description: Log cleaner grows buffers when `result.messagesRead` is zero. In a typical scenari

[jira] [Created] (KAFKA-6855) Kafka fails to start due to faulty Java version detection

Anders Tornblad created KAFKA-6855: -- Summary: Kafka fails to start due to faulty Java version detection Key: KAFKA-6855 URL: https://issues.apache.org/jira/browse/KAFKA-6855 Project: Kafka I

[jira] [Updated] (KAFKA-6854) Log cleaner fails with transaction markers that are deleted during clean

[ https://issues.apache.org/jira/browse/KAFKA-6854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-6854: --- Fix Version/s: 1.1.1 1.0.2 2.0.0 > Log cleaner fails with transa

[jira] [Created] (KAFKA-6854) Log cleaner fails with transaction markers that are deleted during clean

Rajini Sivaram created KAFKA-6854: - Summary: Log cleaner fails with transaction markers that are deleted during clean Key: KAFKA-6854 URL: https://issues.apache.org/jira/browse/KAFKA-6854 Project: Kaf

[jira] [Commented] (KAFKA-6832) Wrong start position in the log file on the leader, on fetch request.

[ https://issues.apache.org/jira/browse/KAFKA-6832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462351#comment-16462351 ] Ciprian Pascu commented on KAFKA-6832: -- Hi, I believe you are right; at the moment,

[jira] [Commented] (KAFKA-5965) Remove Deprecated AdminClient from Streams Resetter Tool

[ https://issues.apache.org/jira/browse/KAFKA-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462325#comment-16462325 ] Alexander Fedosov commented on KAFKA-5965: -- Thank you a lot! > Remove Deprecated

[jira] [Commented] (KAFKA-5965) Remove Deprecated AdminClient from Streams Resetter Tool

[ https://issues.apache.org/jira/browse/KAFKA-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462302#comment-16462302 ] Matthias J. Sax commented on KAFKA-5965: Thanks for your interest in this ticket!

[jira] [Assigned] (KAFKA-5965) Remove Deprecated AdminClient from Streams Resetter Tool

[ https://issues.apache.org/jira/browse/KAFKA-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-5965: -- Assignee: Alexander Fedosov > Remove Deprecated AdminClient from Streams Resetter Tool

[jira] [Commented] (KAFKA-6520) When a Kafka Stream can't communicate with the server, it's Status stays RUNNING

[ https://issues.apache.org/jira/browse/KAFKA-6520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462301#comment-16462301 ] Matthias J. Sax commented on KAFKA-6520: If you can reproduce the issue as describ

[jira] [Commented] (KAFKA-6853) ResponseMetadata calculates latency incorrectly (and therefore ZooKeeperRequestLatencyMs is incorrect)

[ https://issues.apache.org/jira/browse/KAFKA-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462292#comment-16462292 ] ASF GitHub Bot commented on KAFKA-6853: --- Fuud opened a new pull request #4961: KAFKA

[jira] [Updated] (KAFKA-6853) ResponseMetadata calculates latency incorrectly (and therefore ZooKeeperRequestLatencyMs is incorrect)

[ https://issues.apache.org/jira/browse/KAFKA-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fuud updated KAFKA-6853: Summary: ResponseMetadata calculates latency incorrectly (and therefore ZooKeeperRequestLatencyMs is incorrect) (wa

[jira] [Created] (KAFKA-6853) ResponseMetadata calculates latency incorrectly (and therefore ZooKeeperRequestLatencyMs)

Fuud created KAFKA-6853: --- Summary: ResponseMetadata calculates latency incorrectly (and therefore ZooKeeperRequestLatencyMs) Key: KAFKA-6853 URL: https://issues.apache.org/jira/browse/KAFKA-6853 Project: Kafka

[jira] [Commented] (KAFKA-5965) Remove Deprecated AdminClient from Streams Resetter Tool

[ https://issues.apache.org/jira/browse/KAFKA-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462235#comment-16462235 ] Alexander Fedosov commented on KAFKA-5965: -- Hello! I would like to help with this

[jira] [Commented] (KAFKA-6842) initTransactions hangs when trying to connect to non-existing broker

[ https://issues.apache.org/jira/browse/KAFKA-6842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462162#comment-16462162 ] huxihx commented on KAFKA-6842: --- Seems it's a duplicate of [KAFKA-6446|https://issues.apach

[jira] [Commented] (KAFKA-6851) Kafka CLI commands should support specifying the servers in environment variables

[ https://issues.apache.org/jira/browse/KAFKA-6851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462055#comment-16462055 ] Peter Horvath commented on KAFKA-6851: -- My feeling is that the majority of people wor