[jira] [Commented] (KAFKA-6338) java.lang.NoClassDefFoundError: org/apache/kafka/common/network/LoginType

[ https://issues.apache.org/jira/browse/KAFKA-6338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284657#comment-16284657 ] Ronald van de Kuil commented on KAFKA-6338: --- [2017-12-09 06:54:22,233] ERROR Error getting

[jira] [Created] (KAFKA-6338) java.lang.NoClassDefFoundError: org/apache/kafka/common/network/LoginType

Ronald van de Kuil created KAFKA-6338: - Summary: java.lang.NoClassDefFoundError: org/apache/kafka/common/network/LoginType Key: KAFKA-6338 URL: https://issues.apache.org/jira/browse/KAFKA-6338

[jira] [Created] (KAFKA-6337) Error for partition [__consumer_offsets,15] to broker

Abhi created KAFKA-6337: --- Summary: Error for partition [__consumer_offsets,15] to broker Key: KAFKA-6337 URL: https://issues.apache.org/jira/browse/KAFKA-6337 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-4218) Enable access to key in ValueTransformer

[ https://issues.apache.org/jira/browse/KAFKA-4218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284488#comment-16284488 ] ASF GitHub Bot commented on KAFKA-4218: --- GitHub user jeyhunkarimov opened a pull request:

[jira] [Commented] (KAFKA-4218) Enable access to key in ValueTransformer

[ https://issues.apache.org/jira/browse/KAFKA-4218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284486#comment-16284486 ] ASF GitHub Bot commented on KAFKA-4218: --- Github user jeyhunkarimov closed the pull request at:

[jira] [Commented] (KAFKA-6334) Minor documentation typo

[ https://issues.apache.org/jira/browse/KAFKA-6334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284480#comment-16284480 ] Guozhang Wang commented on KAFKA-6334: -- Thanks for the report [~noslowerdna], mind submitting a patch

[jira] [Created] (KAFKA-6336) when using assign() with kafka consumer the KafkaConsumerGroup command doesnt show those consumers

Neerja Khattar created KAFKA-6336: - Summary: when using assign() with kafka consumer the KafkaConsumerGroup command doesnt show those consumers Key: KAFKA-6336 URL:

[jira] [Created] (KAFKA-6335) SimpleAclAuthorizerTest#testHighConcurrencyModificationOfResourceAcls fails intermittently

Ted Yu created KAFKA-6335: - Summary: SimpleAclAuthorizerTest#testHighConcurrencyModificationOfResourceAcls fails intermittently Key: KAFKA-6335 URL: https://issues.apache.org/jira/browse/KAFKA-6335 Project:

[jira] [Commented] (KAFKA-6323) punctuate with WALL_CLOCK_TIME triggered immediately

[ https://issues.apache.org/jira/browse/KAFKA-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284417#comment-16284417 ] Matthias J. Sax commented on KAFKA-6323: We discussed "mix mode" during the KIP

[jira] [Commented] (KAFKA-6323) punctuate with WALL_CLOCK_TIME triggered immediately

[ https://issues.apache.org/jira/browse/KAFKA-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284366#comment-16284366 ] Stephane Maarek commented on KAFKA-6323: Fully agree [~guozhang] . I fully agree on the punctuate

[jira] [Created] (KAFKA-6334) Minor documentation typo

Andrew Olson created KAFKA-6334: --- Summary: Minor documentation typo Key: KAFKA-6334 URL: https://issues.apache.org/jira/browse/KAFKA-6334 Project: Kafka Issue Type: Bug Components:

[jira] [Created] (KAFKA-6333) java.awt.headless should not be on commandline

Fabrice Bacchella created KAFKA-6333: Summary: java.awt.headless should not be on commandline Key: KAFKA-6333 URL: https://issues.apache.org/jira/browse/KAFKA-6333 Project: Kafka Issue

[jira] [Commented] (KAFKA-6307) mBeanName should be removed before returning from JmxReporter#removeAttribute()

[ https://issues.apache.org/jira/browse/KAFKA-6307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284135#comment-16284135 ] siva santhalingam commented on KAFKA-6307: -- [~tedyu] Please go ahead and assign it to yourself.

[jira] [Commented] (KAFKA-6318) StreamsResetter should return non-zero return code on error

[ https://issues.apache.org/jira/browse/KAFKA-6318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284083#comment-16284083 ] Matthias J. Sax commented on KAFKA-6318: Of course you can assign tickets to yourself if it's

[jira] [Assigned] (KAFKA-6318) StreamsResetter should return non-zero return code on error

[ https://issues.apache.org/jira/browse/KAFKA-6318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-6318: -- Assignee: siva santhalingam > StreamsResetter should return non-zero return code on

[jira] [Commented] (KAFKA-6307) mBeanName should be removed before returning from JmxReporter#removeAttribute()

[ https://issues.apache.org/jira/browse/KAFKA-6307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284053#comment-16284053 ] ASF GitHub Bot commented on KAFKA-6307: --- GitHub user tedyu opened a pull request:

[jira] [Commented] (KAFKA-6331) Transient failure in kafka.api.AdminClientIntegrationTest.testLogStartOffsetCheckpointkafka.api.AdminClientIntegrationTest.testAlterReplicaLogDirs

[ https://issues.apache.org/jira/browse/KAFKA-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283995#comment-16283995 ] ASF GitHub Bot commented on KAFKA-6331: --- GitHub user lindong28 opened a pull request:

[jira] [Commented] (KAFKA-6318) StreamsResetter should return non-zero return code on error

[ https://issues.apache.org/jira/browse/KAFKA-6318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283954#comment-16283954 ] ASF GitHub Bot commented on KAFKA-6318: --- GitHub user shivsantham opened a pull request:

[jira] [Commented] (KAFKA-6307) mBeanName should be removed before returning from JmxReporter#removeAttribute()

[ https://issues.apache.org/jira/browse/KAFKA-6307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283925#comment-16283925 ] Ted Yu commented on KAFKA-6307: --- Siva: I have some cycles now. If you haven't started, can I continue

[jira] [Commented] (KAFKA-6323) punctuate with WALL_CLOCK_TIME triggered immediately

[ https://issues.apache.org/jira/browse/KAFKA-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283901#comment-16283901 ] Guozhang Wang commented on KAFKA-6323: -- Here are my thoughts on punctuation semantics (on both

[jira] [Commented] (KAFKA-6323) punctuate with WALL_CLOCK_TIME triggered immediately

[ https://issues.apache.org/jira/browse/KAFKA-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283863#comment-16283863 ] Guozhang Wang commented on KAFKA-6323: -- [~frederica] I have added you to the contributor list. You

[jira] [Assigned] (KAFKA-6323) punctuate with WALL_CLOCK_TIME triggered immediately

[ https://issues.apache.org/jira/browse/KAFKA-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-6323: Assignee: Frederic Arno > punctuate with WALL_CLOCK_TIME triggered immediately >

[jira] [Resolved] (KAFKA-5002) Stream does't seem to consider partitions for processing which are being consumed

[ https://issues.apache.org/jira/browse/KAFKA-5002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-5002. -- Resolution: Not A Problem > Stream does't seem to consider partitions for processing which are

[jira] [Commented] (KAFKA-5868) Kafka Consumer Rebalancing takes too long

[ https://issues.apache.org/jira/browse/KAFKA-5868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283857#comment-16283857 ] Guozhang Wang commented on KAFKA-5868: -- [~nandishkotadia] Have you tried the newer version {{1.0.0}}

[jira] [Commented] (KAFKA-6237) stream stopped working after exception: Cannot execute transactional method because we are in an error state

[ https://issues.apache.org/jira/browse/KAFKA-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283845#comment-16283845 ] Guozhang Wang commented on KAFKA-6237: -- There is no broker issue I think, note that

[jira] [Resolved] (KAFKA-5702) Refactor StreamThread to separate concerns and enable better testability

[ https://issues.apache.org/jira/browse/KAFKA-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-5702. -- Resolution: Fixed > Refactor StreamThread to separate concerns and enable better testability >

[jira] [Commented] (KAFKA-4706) Unify StreamsKafkaClient instances

[ https://issues.apache.org/jira/browse/KAFKA-4706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283819#comment-16283819 ] Guozhang Wang commented on KAFKA-4706: -- [~sharad.develop] StreamsKafkaClient has been replaced with

[jira] [Commented] (KAFKA-6331) Transient failure in kafka.api.AdminClientIntegrationTest.testLogStartOffsetCheckpointkafka.api.AdminClientIntegrationTest.testAlterReplicaLogDirs

[ https://issues.apache.org/jira/browse/KAFKA-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283786#comment-16283786 ] Ismael Juma commented on KAFKA-6331: cc [~lindong] > Transient failure in >

[jira] [Created] (KAFKA-6332) Kafka system tests should use nc instead of log grep to detect start-up

Ismael Juma created KAFKA-6332: -- Summary: Kafka system tests should use nc instead of log grep to detect start-up Key: KAFKA-6332 URL: https://issues.apache.org/jira/browse/KAFKA-6332 Project: Kafka

[jira] [Created] (KAFKA-6331) Transient failure in kafka.api.AdminClientIntegrationTest.testLogStartOffsetCheckpointkafka.api.AdminClientIntegrationTest.testAlterReplicaLogDirs

Guozhang Wang created KAFKA-6331: Summary: Transient failure in kafka.api.AdminClientIntegrationTest.testLogStartOffsetCheckpointkafka.api.AdminClientIntegrationTest.testAlterReplicaLogDirs Key: KAFKA-6331 URL:

[jira] [Updated] (KAFKA-6330) KafkaZkClient request queue time metric

[ https://issues.apache.org/jira/browse/KAFKA-6330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-6330: --- Issue Type: Sub-task (was: Bug) Parent: KAFKA-5027 > KafkaZkClient request queue time metric

[jira] [Updated] (KAFKA-6320) move ZK metrics in KafkaHealthCheck to ZookeeperClient

[ https://issues.apache.org/jira/browse/KAFKA-6320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-6320: --- Fix Version/s: 1.1.0 > move ZK metrics in KafkaHealthCheck to ZookeeperClient >

[jira] [Created] (KAFKA-6330) KafkaZkClient request queue time metric

Ismael Juma created KAFKA-6330: -- Summary: KafkaZkClient request queue time metric Key: KAFKA-6330 URL: https://issues.apache.org/jira/browse/KAFKA-6330 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-5200) If a replicated topic is deleted with one broker down, it can't be recreated

[ https://issues.apache.org/jira/browse/KAFKA-5200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283713#comment-16283713 ] Matthias Rampke commented on KAFKA-5200: To expand on the workaround [~huxi_2b] proposed: If you

[jira] [Commented] (KAFKA-6325) Producer.flush() doesn't throw exception on timeout

[ https://issues.apache.org/jira/browse/KAFKA-6325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283444#comment-16283444 ] Erik Scheuter commented on KAFKA-6325: -- I didn't modify the KafkaProducer, but the code which uses it

[jira] [Resolved] (KAFKA-6289) NetworkClient should not return internal failed api version responses from poll

[ https://issues.apache.org/jira/browse/KAFKA-6289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-6289. --- Resolution: Fixed Fix Version/s: 1.0.1 1.1.0 Issue resolved by pull

[jira] [Commented] (KAFKA-6289) NetworkClient should not return internal failed api version responses from poll

[ https://issues.apache.org/jira/browse/KAFKA-6289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283362#comment-16283362 ] ASF GitHub Bot commented on KAFKA-6289: --- Github user asfgit closed the pull request at:

[jira] [Commented] (KAFKA-6266) Kafka 1.0.0 : Repeated occurrence of WARN Resetting first dirty offset of __consumer_offsets-xx to log start offset 203569 since the checkpointed offset 120955 is inval

[ https://issues.apache.org/jira/browse/KAFKA-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283358#comment-16283358 ] Ismael Juma commented on KAFKA-6266: cc [~junrao] > Kafka 1.0.0 : Repeated occurrence of WARN

[jira] [Commented] (KAFKA-6314) Add a tool to delete kafka based consumer offsets for a given group

[ https://issues.apache.org/jira/browse/KAFKA-6314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283277#comment-16283277 ] Tom Scott commented on KAFKA-6314: -- thank, I've modified it to reference kafka based offsets > Add a

[jira] [Updated] (KAFKA-6314) Add a tool to delete kafka based consumer offsets for a given group

[ https://issues.apache.org/jira/browse/KAFKA-6314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Scott updated KAFKA-6314: - Description: Add a tool to delete kafka based consumer offsets for a given group similar to the reset

[jira] [Updated] (KAFKA-6314) Add a tool to delete kafka based consumer offsets for a given group

[ https://issues.apache.org/jira/browse/KAFKA-6314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Scott updated KAFKA-6314: - Summary: Add a tool to delete kafka based consumer offsets for a given group (was: Add a tool to delete

[jira] [Commented] (KAFKA-6314) Add a tool to delete consumer offsets for a given group

[ https://issues.apache.org/jira/browse/KAFKA-6314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283235#comment-16283235 ] James Cheng commented on KAFKA-6314: FYI, kafka-consumer-groups.sh already has --delete support, but

[jira] [Comment Edited] (KAFKA-6326) when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout

[ https://issues.apache.org/jira/browse/KAFKA-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283207#comment-16283207 ] HongLiang edited comment on KAFKA-6326 at 12/8/17 8:37 AM: ---

[jira] [Commented] (KAFKA-6326) when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout

[ https://issues.apache.org/jira/browse/KAFKA-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283207#comment-16283207 ] HongLiang commented on KAFKA-6326: -- [~huxi_2b][{color:red}2017-10-30 14:15:18,009{color}]

[jira] [Commented] (KAFKA-6326) when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout

[ https://issues.apache.org/jira/browse/KAFKA-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283197#comment-16283197 ] huxihx commented on KAFKA-6326: --- [~HongLiang] Could you offer the exact timestamp when shutting down the