[jira] [Commented] (KAFKA-7322) race between compaction thread and retention thread when changing topic cleanup policy

[ https://issues.apache.org/jira/browse/KAFKA-7322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588450#comment-16588450 ] Dhruvil Shah commented on KAFKA-7322: - Does this issue still exist after KAFKA-7278 w

[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=16588446#comment-16588446 ] Harald Kirsch commented on KAFKA-1194: -- Most likely, and if the root cause is [http

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

[ https://issues.apache.org/jira/browse/KAFKA-5998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588406#comment-16588406 ] Ayushi edited comment on KAFKA-5998 at 8/22/18 5:33 AM: [~guozhan

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

[ https://issues.apache.org/jira/browse/KAFKA-5998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588406#comment-16588406 ] Ayushi edited comment on KAFKA-5998 at 8/22/18 5:33 AM: [~guozhan

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

[ https://issues.apache.org/jira/browse/KAFKA-5998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588406#comment-16588406 ] Ayushi commented on KAFKA-5998: --- [~guozhang] This issue is there in 2.0.0 as well > /.chec

[jira] [Commented] (KAFKA-7190) Under low traffic conditions purging repartition topics cause WARN statements about UNKNOWN_PRODUCER_ID

[ https://issues.apache.org/jira/browse/KAFKA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588383#comment-16588383 ] Matthias J. Sax commented on KAFKA-7190: [~guozhang] From my understanding, if UN

[jira] [Commented] (KAFKA-7190) Under low traffic conditions purging repartition topics cause WARN statements about UNKNOWN_PRODUCER_ID

[ https://issues.apache.org/jira/browse/KAFKA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588370#comment-16588370 ] Guozhang Wang commented on KAFKA-7190: -- [~lambdaliu] As Jason's proposal #5 mentione

[jira] [Commented] (KAFKA-7324) NPE due to lack of SASLExtensions in SASL/OAUTHBEARER

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

[jira] [Created] (KAFKA-7324) NPE due to lack of SASLExtensions in SASL/OAUTHBEARER

Ron Dagostino created KAFKA-7324: Summary: NPE due to lack of SASLExtensions in SASL/OAUTHBEARER Key: KAFKA-7324 URL: https://issues.apache.org/jira/browse/KAFKA-7324 Project: Kafka Issue Typ

[jira] [Created] (KAFKA-7323) add replication factor doesn't work

superheizai created KAFKA-7323: -- Summary: add replication factor doesn't work Key: KAFKA-7323 URL: https://issues.apache.org/jira/browse/KAFKA-7323 Project: Kafka Issue Type: Bug Compo

[jira] [Commented] (KAFKA-6753) Speed up event processing on the controller

[ https://issues.apache.org/jira/browse/KAFKA-6753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588220#comment-16588220 ] Jun Rao commented on KAFKA-6753: [~luwang], that sounds good too. To make tracking easier

[jira] [Reopened] (KAFKA-6753) Speed up event processing on the controller

[ https://issues.apache.org/jira/browse/KAFKA-6753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucas Wang reopened KAFKA-6753: --- > Speed up event processing on the controller > > >

[jira] [Commented] (KAFKA-6753) Speed up event processing on the controller

[ https://issues.apache.org/jira/browse/KAFKA-6753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588186#comment-16588186 ] Lucas Wang commented on KAFKA-6753: --- [~junrao] Personally I'm in favor of removing this

[jira] [Comment Edited] (KAFKA-7316) Use of filter method in KTable.scala may result in StackOverflowError

[ https://issues.apache.org/jira/browse/KAFKA-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586909#comment-16586909 ] Ted Yu edited comment on KAFKA-7316 at 8/22/18 12:20 AM: - Patch v

[jira] [Commented] (KAFKA-7190) Under low traffic conditions purging repartition topics cause WARN statements about UNKNOWN_PRODUCER_ID

[ https://issues.apache.org/jira/browse/KAFKA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588173#comment-16588173 ] Jason Gustafson commented on KAFKA-7190: [~lambdaliu] Yeah, I think maintaining t

[jira] [Created] (KAFKA-7322) race between compaction thread and retention thread when changing topic cleanup policy

xiongqi wu created KAFKA-7322: - Summary: race between compaction thread and retention thread when changing topic cleanup policy Key: KAFKA-7322 URL: https://issues.apache.org/jira/browse/KAFKA-7322 Projec

[jira] [Assigned] (KAFKA-7321) ensure timely processing of deletion requests in Kafka topic (Time-based log compaction)

[ https://issues.apache.org/jira/browse/KAFKA-7321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiongqi wu reassigned KAFKA-7321: - Assignee: xiongqi wu > ensure timely processing of deletion requests in Kafka topic (Time-based

[jira] [Created] (KAFKA-7321) ensure timely processing of deletion requests in Kafka topic (Time-based log compaction)

xiongqi wu created KAFKA-7321: - Summary: ensure timely processing of deletion requests in Kafka topic (Time-based log compaction) Key: KAFKA-7321 URL: https://issues.apache.org/jira/browse/KAFKA-7321 Proj

[jira] [Updated] (KAFKA-7301) KTable to KTable join invocation does not resolve in Scala DSL

[ https://issues.apache.org/jira/browse/KAFKA-7301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-7301: - Fix Version/s: 2.0.1 > KTable to KTable join invocation does not resolve in Scala DSL > -

[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=16588155#comment-16588155 ] Charith Fernando commented on KAFKA-1194: - Will this work If I run on a windows c

[jira] [Updated] (KAFKA-7317) Use collections subscription for main consumer to reduce metadata

[ https://issues.apache.org/jira/browse/KAFKA-7317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-7317: --- Description: In KAFKA-4633 we switched from "collection subscription" to "pattern subscripti

[jira] [Resolved] (KAFKA-7301) KTable to KTable join invocation does not resolve in Scala DSL

[ https://issues.apache.org/jira/browse/KAFKA-7301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-7301. -- Resolution: Fixed Fix Version/s: 2.1.0 > KTable to KTable join invocation does not resol

[jira] [Commented] (KAFKA-7301) KTable to KTable join invocation does not resolve in Scala DSL

[ https://issues.apache.org/jira/browse/KAFKA-7301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588106#comment-16588106 ] ASF GitHub Bot commented on KAFKA-7301: --- guozhangwang closed pull request #5502: KA

[jira] [Created] (KAFKA-7320) Provide ability to disable auto topic creation in KafkaConsumer

Dhruvil Shah created KAFKA-7320: --- Summary: Provide ability to disable auto topic creation in KafkaConsumer Key: KAFKA-7320 URL: https://issues.apache.org/jira/browse/KAFKA-7320 Project: Kafka

[jira] [Assigned] (KAFKA-5295) Allow Kafka Connect source connectors to specify topic-specific settings for new topics

[ https://issues.apache.org/jira/browse/KAFKA-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch reassigned KAFKA-5295: Assignee: Randall Hauch (was: Magesh kumar Nandakumar) > Allow Kafka Connect source conne

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

[ https://issues.apache.org/jira/browse/KAFKA-7290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588030#comment-16588030 ] Guozhang Wang commented on KAFKA-7290: -- The metadata request sent to brokers look no

[jira] [Commented] (KAFKA-6753) Speed up event processing on the controller

[ https://issues.apache.org/jira/browse/KAFKA-6753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588026#comment-16588026 ] Jun Rao commented on KAFKA-6753: [~luwang], we could consider removing this metric, but i

[jira] [Commented] (KAFKA-5407) Mirrormaker dont start after upgrade

[ https://issues.apache.org/jira/browse/KAFKA-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588019#comment-16588019 ] Fernando Vega commented on KAFKA-5407: -- Thx for the suggestions. We finally fix this

[jira] [Resolved] (KAFKA-5407) Mirrormaker dont start after upgrade

[ https://issues.apache.org/jira/browse/KAFKA-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fernando Vega resolved KAFKA-5407. -- Resolution: Fixed > Mirrormaker dont start after upgrade >

[jira] [Commented] (KAFKA-7063) Update documentation to remove references to old producers and consumers

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

[jira] [Commented] (KAFKA-6753) Speed up event processing on the controller

[ https://issues.apache.org/jira/browse/KAFKA-6753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587994#comment-16587994 ] Lucas Wang commented on KAFKA-6753: --- Hi [~junrao] thanks reviewing the PR. Besides the

[jira] [Commented] (KAFKA-7316) Use of filter method in KTable.scala may result in StackOverflowError

[ https://issues.apache.org/jira/browse/KAFKA-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587961#comment-16587961 ] Ted Yu commented on KAFKA-7316: --- I closed my PR since there was an earlier PR addressing th

[jira] [Commented] (KAFKA-7316) Use of filter method in KTable.scala may result in StackOverflowError

[ https://issues.apache.org/jira/browse/KAFKA-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587959#comment-16587959 ] ASF GitHub Bot commented on KAFKA-7316: --- tedyu closed pull request #5543: KAFKA-731

[jira] [Commented] (KAFKA-6904) DynamicBrokerReconfigurationTest#testAdvertisedListenerUpdate is flaky

[ https://issues.apache.org/jira/browse/KAFKA-6904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587957#comment-16587957 ] Ted Yu commented on KAFKA-6904: --- In the above test output, there was: {code} 2018-08-21 18:

[jira] [Commented] (KAFKA-6904) DynamicBrokerReconfigurationTest#testAdvertisedListenerUpdate is flaky

[ https://issues.apache.org/jira/browse/KAFKA-6904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587955#comment-16587955 ] Ted Yu commented on KAFKA-6904: --- testUncleanLeaderElectionEnable was the latest which may f

[jira] [Issue Comment Deleted] (KAFKA-7316) Use of filter method in KTable.scala may result in StackOverflowError

[ https://issues.apache.org/jira/browse/KAFKA-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated KAFKA-7316: -- Comment: was deleted (was: I was thinking about removing the implicit wrapKTable . Then the following compilati

[jira] [Issue Comment Deleted] (KAFKA-7316) Use of filter method in KTable.scala may result in StackOverflowError

[ https://issues.apache.org/jira/browse/KAFKA-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated KAFKA-7316: -- Comment: was deleted (was: Patch v2 reduces compilation errors to 20.) > Use of filter method in KTable.scala

[jira] [Issue Comment Deleted] (KAFKA-7316) Use of filter method in KTable.scala may result in StackOverflowError

[ https://issues.apache.org/jira/browse/KAFKA-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated KAFKA-7316: -- Comment: was deleted (was: [~guozhang] [~mjsax] : Can you take a look at patch v1 to see if the changes to Ses

[jira] [Commented] (KAFKA-7165) Error while creating ephemeral at /brokers/ids/BROKER_ID

[ https://issues.apache.org/jira/browse/KAFKA-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587940#comment-16587940 ] Jonathan Santilli commented on KAFKA-7165: -- Hi, [~omkreddy] [~ijuma], am working

[jira] [Commented] (KAFKA-7214) Mystic FATAL error

[ https://issues.apache.org/jira/browse/KAFKA-7214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587904#comment-16587904 ] Guozhang Wang commented on KAFKA-7214: -- Could you confirm if in 1.1.1 the above erro

[jira] [Commented] (KAFKA-7214) Mystic FATAL error

[ https://issues.apache.org/jira/browse/KAFKA-7214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587902#comment-16587902 ] Guozhang Wang commented on KAFKA-7214: -- [~habdank] The issue reported in the origina

[jira] [Created] (KAFKA-7319) Add documentation for consumer group management

Manikumar created KAFKA-7319: Summary: Add documentation for consumer group management Key: KAFKA-7319 URL: https://issues.apache.org/jira/browse/KAFKA-7319 Project: Kafka Issue Type: Task

[jira] [Updated] (KAFKA-6753) Speed up event processing on the controller

[ https://issues.apache.org/jira/browse/KAFKA-6753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucas Wang updated KAFKA-6753: -- Description: The existing controller code updates metrics after processing every event. This can slow

[jira] [Resolved] (KAFKA-6753) Speed up event processing on the controller

[ https://issues.apache.org/jira/browse/KAFKA-6753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-6753. Resolution: Fixed Fix Version/s: 2.1.0 Merged the PR to trunk. > Speed up event processing on the c

[jira] [Commented] (KAFKA-6753) Speed up event processing on the controller

[ https://issues.apache.org/jira/browse/KAFKA-6753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587845#comment-16587845 ] ASF GitHub Bot commented on KAFKA-6753: --- junrao closed pull request #5388: KAFKA-67

[jira] [Assigned] (KAFKA-7286) Loading offsets and group metadata hangs with large group metadata records

[ https://issues.apache.org/jira/browse/KAFKA-7286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavien Raynaud reassigned KAFKA-7286: -- Assignee: Flavien Raynaud > Loading offsets and group metadata hangs with large group

[jira] [Updated] (KAFKA-7284) Producer getting fenced may cause Streams to shut down

[ https://issues.apache.org/jira/browse/KAFKA-7284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-7284: --- Fix Version/s: 1.0.3 0.11.0.4 > Producer getting fenced may cause Streams

[jira] [Commented] (KAFKA-7284) Producer getting fenced may cause Streams to shut down

[ https://issues.apache.org/jira/browse/KAFKA-7284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587752#comment-16587752 ] ASF GitHub Bot commented on KAFKA-7284: --- mjsax closed pull request #5520: KAFKA-728

[jira] [Commented] (KAFKA-7214) Mystic FATAL error

[ https://issues.apache.org/jira/browse/KAFKA-7214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587749#comment-16587749 ] Matthias J. Sax commented on KAFKA-7214: Hmmm... not sure. However, is seems that

[jira] [Commented] (KAFKA-7315) Streams serialization docs contain a broken link for Avro

[ https://issues.apache.org/jira/browse/KAFKA-7315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587711#comment-16587711 ] Matthias J. Sax commented on KAFKA-7315: That's a fair point. Feel free to do a P

[jira] [Updated] (KAFKA-7316) Use of filter method in KTable.scala may result in StackOverflowError

[ https://issues.apache.org/jira/browse/KAFKA-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated KAFKA-7316: -- Attachment: (was: 7316.v1.txt) > Use of filter method in KTable.scala may result in StackOverflowError > --

[jira] [Updated] (KAFKA-7316) Use of filter method in KTable.scala may result in StackOverflowError

[ https://issues.apache.org/jira/browse/KAFKA-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated KAFKA-7316: -- Attachment: (was: 7316.v2.txt) > Use of filter method in KTable.scala may result in StackOverflowError > --

[jira] [Commented] (KAFKA-7318) Should introduce a offset reset policy to consume only the messages after subscribing

[ https://issues.apache.org/jira/browse/KAFKA-7318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587689#comment-16587689 ] Matthias J. Sax commented on KAFKA-7318: > {{latest}} (the default) , if a consum

[jira] [Commented] (KAFKA-7315) Streams serialization docs contain a broken link for Avro

[ https://issues.apache.org/jira/browse/KAFKA-7315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587602#comment-16587602 ] Jordan Moore commented on KAFKA-7315: - I understand the "Serde" class itself is a Str

[jira] [Comment Edited] (KAFKA-7315) Streams serialization docs contain a broken link for Avro

[ https://issues.apache.org/jira/browse/KAFKA-7315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587602#comment-16587602 ] Jordan Moore edited comment on KAFKA-7315 at 8/21/18 3:38 PM: -

[jira] [Commented] (KAFKA-6033) Kafka Streams does not work with musl-libc (alpine linux)

[ https://issues.apache.org/jira/browse/KAFKA-6033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587598#comment-16587598 ] John Roesler commented on KAFKA-6033: - This is, unfortunately, correct, and there's n

[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=16587596#comment-16587596 ] Dong Lin commented on KAFKA-6188: - [~TeilaRei] I think the discussion for the fix is in

[jira] [Commented] (KAFKA-5891) Cast transformation fails if record schema contains timestamp field

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

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

[ https://issues.apache.org/jira/browse/KAFKA-7290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587568#comment-16587568 ] John Roesler commented on KAFKA-7290: - I know the circumstances with that rocks excep

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

[ https://issues.apache.org/jira/browse/KAFKA-7290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587554#comment-16587554 ] John Roesler commented on KAFKA-7290: - These are just the logs for one Streams proces

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

[ https://issues.apache.org/jira/browse/KAFKA-7290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587551#comment-16587551 ] John Roesler commented on KAFKA-7290: - Also the network selector's node ids look funn

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

[ https://issues.apache.org/jira/browse/KAFKA-7290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587544#comment-16587544 ] John Roesler edited comment on KAFKA-7290 at 8/21/18 2:55 PM: -

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

[ https://issues.apache.org/jira/browse/KAFKA-7290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587544#comment-16587544 ] John Roesler commented on KAFKA-7290: - There's one thread, and two consumers: 2018-0

[jira] [Commented] (KAFKA-7214) Mystic FATAL error

[ https://issues.apache.org/jira/browse/KAFKA-7214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587475#comment-16587475 ] Seweryn Habdank-Wojewodzki commented on KAFKA-7214: --- Hi, I had updated

[jira] [Updated] (KAFKA-7214) Mystic FATAL error

[ https://issues.apache.org/jira/browse/KAFKA-7214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seweryn Habdank-Wojewodzki updated KAFKA-7214: -- Affects Version/s: 1.1.1 > Mystic FATAL error > -- > >

[jira] [Comment Edited] (KAFKA-7214) Mystic FATAL error

[ https://issues.apache.org/jira/browse/KAFKA-7214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587475#comment-16587475 ] Seweryn Habdank-Wojewodzki edited comment on KAFKA-7214 at 8/21/18 2:11 PM: ---

[jira] [Comment Edited] (KAFKA-7214) Mystic FATAL error

[ https://issues.apache.org/jira/browse/KAFKA-7214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587475#comment-16587475 ] Seweryn Habdank-Wojewodzki edited comment on KAFKA-7214 at 8/21/18 2:10 PM: ---

[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=16587381#comment-16587381 ] Valentina Baljak commented on KAFKA-6188: - [~lindong] what exactly is the fix the

[jira] [Commented] (KAFKA-6914) Kafka Connect - Plugins class should have a constructor that can take in parent ClassLoader

[ https://issues.apache.org/jira/browse/KAFKA-6914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587203#comment-16587203 ] Frank Lyaruu commented on KAFKA-6914: - Is there any progress on this? Anything I can

[jira] [Resolved] (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:all-tabpanel ] Dong Lin resolved KAFKA-6188. - Resolution: Fixed Likely fixed in https://issues.apache.org/jira/browse/KAFKA-7278. > Broker fails with

[jira] [Commented] (KAFKA-7278) replaceSegments() should not call asyncDeleteSegment() for segments which have been removed from segments list

[ https://issues.apache.org/jira/browse/KAFKA-7278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587106#comment-16587106 ] ASF GitHub Bot commented on KAFKA-7278: --- lindong28 closed pull request #5535: Cherr