[jira] [Resolved] (KAFKA-7369) Retry when possible in AdminClient.listConsumerGroups

[ https://issues.apache.org/jira/browse/KAFKA-7369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7369. Resolution: Fixed Fix Version/s: 2.1.0 2.0.1 > Retry when possibl

[jira] [Commented] (KAFKA-7369) Retry when possible in AdminClient.listConsumerGroups

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

[jira] [Commented] (KAFKA-7370) Enhance FileConfigProvider to read a directory

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

[jira] [Created] (KAFKA-7370) Enhance FileConfigProvider to read a directory

Robert Yokota created KAFKA-7370: Summary: Enhance FileConfigProvider to read a directory Key: KAFKA-7370 URL: https://issues.apache.org/jira/browse/KAFKA-7370 Project: Kafka Issue Type: Impr

[jira] [Commented] (KAFKA-7369) Retry when possible in AdminClient.listConsumerGroups

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

[jira] [Created] (KAFKA-7369) Retry when possible in AdminClient.listConsumerGroups

Jason Gustafson created KAFKA-7369: -- Summary: Retry when possible in AdminClient.listConsumerGroups Key: KAFKA-7369 URL: https://issues.apache.org/jira/browse/KAFKA-7369 Project: Kafka Issue

[jira] [Resolved] (KAFKA-7287) Set open ACL permissions for old consumer znode path

[ https://issues.apache.org/jira/browse/KAFKA-7287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-7287. Resolution: Fixed Fix Version/s: 2.1.0 2.0.1 1.1.2 Also merged

[jira] [Commented] (KAFKA-7287) Set open ACL permissions for old consumer znode path

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

[jira] [Created] (KAFKA-7368) Support joining Windowed KTables

John Roesler created KAFKA-7368: --- Summary: Support joining Windowed KTables Key: KAFKA-7368 URL: https://issues.apache.org/jira/browse/KAFKA-7368 Project: Kafka Issue Type: Improvement

[jira] [Updated] (KAFKA-7367) Verify that Streams never creates RocksDB stores unless they are needed

[ https://issues.apache.org/jira/browse/KAFKA-7367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-7367: Labels: newbie (was: ) > Verify that Streams never creates RocksDB stores unless they are needed >

[jira] [Created] (KAFKA-7367) Verify that Streams never creates RocksDB stores unless they are needed

John Roesler created KAFKA-7367: --- Summary: Verify that Streams never creates RocksDB stores unless they are needed Key: KAFKA-7367 URL: https://issues.apache.org/jira/browse/KAFKA-7367 Project: Kafka

[jira] [Commented] (KAFKA-3596) Kafka Streams: Window expiration needs to consider more than event time

[ https://issues.apache.org/jira/browse/KAFKA-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16599108#comment-16599108 ] John Roesler commented on KAFKA-3596: - This should be fixed by a few changes coming i

[jira] [Updated] (KAFKA-3596) Kafka Streams: Window expiration needs to consider more than event time

[ https://issues.apache.org/jira/browse/KAFKA-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-3596: Fix Version/s: 2.1.0 > Kafka Streams: Window expiration needs to consider more than event time > --

[jira] [Resolved] (KAFKA-4988) JVM crash when running on Alpine Linux

[ https://issues.apache.org/jira/browse/KAFKA-4988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler resolved KAFKA-4988. - Resolution: Won't Fix I think this issue is out of our hands. If you think there is something fo

[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=16599098#comment-16599098 ] John Roesler commented on KAFKA-6033: - Also, I've just found https://issues.apache.or

[jira] [Resolved] (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:all-tabpanel ] John Roesler resolved KAFKA-6033. - Resolution: Won't Fix This is unfortunately out of our hands. If you think I'm wrong about this,

[jira] [Commented] (KAFKA-4544) Add system tests for delegation token based authentication

[ https://issues.apache.org/jira/browse/KAFKA-4544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16599038#comment-16599038 ] Manikumar commented on KAFKA-4544: -- [~asasvari] If you are interested, Please takeover

[jira] [Commented] (KAFKA-7366) topic level segment.bytes and segment.ms not taking effect immediately

[ https://issues.apache.org/jira/browse/KAFKA-7366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16599003#comment-16599003 ] Jun Rao commented on KAFKA-7366: [~ijuma], it might be debatable. However, if all other t

[jira] [Commented] (KAFKA-7366) topic level segment.bytes and segment.ms not taking effect immediately

[ https://issues.apache.org/jira/browse/KAFKA-7366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598993#comment-16598993 ] Ismael Juma commented on KAFKA-7366: [~rsivaram] noticed this while working on dynami

[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=16598992#comment-16598992 ] John Roesler commented on KAFKA-7214: - Hi [~habdank], I've commented on https://issu

[jira] [Updated] (KAFKA-7366) topic level segment.bytes and segment.ms not taking effect immediately

[ https://issues.apache.org/jira/browse/KAFKA-7366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-7366: --- Affects Version/s: 2.0.0 > topic level segment.bytes and segment.ms not taking effect immediately > -

[jira] [Commented] (KAFKA-7364) kafka periodically run into high cpu usage with ssl writing

[ https://issues.apache.org/jira/browse/KAFKA-7364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598988#comment-16598988 ] Ismael Juma commented on KAFKA-7364: If you have 20k producers all connecting at the

[jira] [Created] (KAFKA-7366) topic level segment.bytes and segment.ms not taking effect immediately

Jun Rao created KAFKA-7366: -- Summary: topic level segment.bytes and segment.ms not taking effect immediately Key: KAFKA-7366 URL: https://issues.apache.org/jira/browse/KAFKA-7366 Project: Kafka Iss

[jira] [Commented] (KAFKA-7364) kafka periodically run into high cpu usage with ssl writing

[ https://issues.apache.org/jira/browse/KAFKA-7364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598981#comment-16598981 ] Ismael Juma commented on KAFKA-7364: Is this specific to ECDSA or all signature types

[jira] [Commented] (KAFKA-6777) Wrong reaction on Out Of Memory situation

[ https://issues.apache.org/jira/browse/KAFKA-6777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598974#comment-16598974 ] John Roesler commented on KAFKA-6777: - Hi [~habdank], It's unfortunately a common be

[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=16598948#comment-16598948 ] Dong Lin commented on KAFKA-7278: - [~niob] The stacktrace in that Jira seems similar to t

[jira] [Commented] (KAFKA-7363) How num.stream.threads in streaming application influence memory consumption?

[ https://issues.apache.org/jira/browse/KAFKA-7363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598941#comment-16598941 ] John Roesler commented on KAFKA-7363: - I'm not sure what other information we can pro

[jira] [Commented] (KAFKA-7363) How num.stream.threads in streaming application influence memory consumption?

[ https://issues.apache.org/jira/browse/KAFKA-7363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598938#comment-16598938 ] John Roesler commented on KAFKA-7363: - Hi Seweryn,   It's a little hard to say. For o

[jira] [Updated] (KAFKA-7363) How num.stream.threads in streaming application influence memory consumption?

[ https://issues.apache.org/jira/browse/KAFKA-7363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-7363: Component/s: streams > How num.stream.threads in streaming application influence memory consumption

[jira] [Commented] (KAFKA-1880) Add support for checking binary/source compatibility

[ https://issues.apache.org/jira/browse/KAFKA-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598830#comment-16598830 ] Viktor Somogyi commented on KAFKA-1880: --- [~granthenke] if you don't mind I've reass

[jira] [Assigned] (KAFKA-1880) Add support for checking binary/source compatibility

[ https://issues.apache.org/jira/browse/KAFKA-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi reassigned KAFKA-1880: - Assignee: Viktor Somogyi (was: Grant Henke) > Add support for checking binary/source co

[jira] [Comment Edited] (KAFKA-7365) max.poll.records setting in Kafka Consumer is not working

[ https://issues.apache.org/jira/browse/KAFKA-7365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598591#comment-16598591 ] M. Manna edited comment on KAFKA-7365 at 8/31/18 12:06 PM: --- [~k

[jira] [Comment Edited] (KAFKA-7365) max.poll.records setting in Kafka Consumer is not working

[ https://issues.apache.org/jira/browse/KAFKA-7365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598591#comment-16598591 ] M. Manna edited comment on KAFKA-7365 at 8/31/18 12:06 PM: --- [~k

[jira] [Comment Edited] (KAFKA-7365) max.poll.records setting in Kafka Consumer is not working

[ https://issues.apache.org/jira/browse/KAFKA-7365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598591#comment-16598591 ] M. Manna edited comment on KAFKA-7365 at 8/31/18 12:04 PM: --- [~k

[jira] [Comment Edited] (KAFKA-7365) max.poll.records setting in Kafka Consumer is not working

[ https://issues.apache.org/jira/browse/KAFKA-7365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598591#comment-16598591 ] M. Manna edited comment on KAFKA-7365 at 8/31/18 11:58 AM: --- [~k

[jira] [Comment Edited] (KAFKA-7365) max.poll.records setting in Kafka Consumer is not working

[ https://issues.apache.org/jira/browse/KAFKA-7365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598591#comment-16598591 ] M. Manna edited comment on KAFKA-7365 at 8/31/18 11:57 AM: --- [~k

[jira] [Comment Edited] (KAFKA-7365) max.poll.records setting in Kafka Consumer is not working

[ https://issues.apache.org/jira/browse/KAFKA-7365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598591#comment-16598591 ] M. Manna edited comment on KAFKA-7365 at 8/31/18 11:55 AM: --- [~k

[jira] [Commented] (KAFKA-6950) Add mechanism to delay response to failed client authentication

[ https://issues.apache.org/jira/browse/KAFKA-6950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598593#comment-16598593 ] ASF GitHub Bot commented on KAFKA-6950: --- rajinisivaram closed pull request #5082: K

[jira] [Commented] (KAFKA-7365) max.poll.records setting in Kafka Consumer is not working

[ https://issues.apache.org/jira/browse/KAFKA-7365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598591#comment-16598591 ] M. Manna commented on KAFKA-7365: - [~kivaturi] I am not sure how your heartbeat interval

[jira] [Commented] (KAFKA-4544) Add system tests for delegation token based authentication

[ https://issues.apache.org/jira/browse/KAFKA-4544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598557#comment-16598557 ] Attila Sasvari commented on KAFKA-4544: --- Do you have the capacity to work on this [

[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=16598540#comment-16598540 ] Christoph Schmidt commented on KAFKA-7278: -- This ticket has raised questions in

[jira] [Created] (KAFKA-7365) max.poll.records setting in Kafka Consumer is not working

Kashyap Ivaturi created KAFKA-7365: -- Summary: max.poll.records setting in Kafka Consumer is not working Key: KAFKA-7365 URL: https://issues.apache.org/jira/browse/KAFKA-7365 Project: Kafka I