[jira] [Commented] (KAFKA-6873) Broker is not returning data including requested offset

[ https://issues.apache.org/jira/browse/KAFKA-6873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482623#comment-16482623 ] Jason Gustafson commented on KAFKA-6873: If a fetch offset lands in the middle of a batch of

[jira] [Commented] (KAFKA-6926) Reduce NPath exceptions in Connect

[ https://issues.apache.org/jira/browse/KAFKA-6926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482703#comment-16482703 ] ASF GitHub Bot commented on KAFKA-6926: --- rhauch opened a new pull request #5051: KAFKA-6926:

[jira] [Updated] (KAFKA-3816) Provide more context in Kafka Connect log messages using MDC

[ https://issues.apache.org/jira/browse/KAFKA-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-3816: - Summary: Provide more context in Kafka Connect log messages using MDC (was: Provide more context

[jira] [Assigned] (KAFKA-6926) Reduce NPath exceptions in Connect

[ https://issues.apache.org/jira/browse/KAFKA-6926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch reassigned KAFKA-6926: Assignee: Randall Hauch > Reduce NPath exceptions in Connect >

[jira] [Commented] (KAFKA-6868) BufferUnderflowException in client when querying consumer group information

[ https://issues.apache.org/jira/browse/KAFKA-6868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482631#comment-16482631 ] ASF GitHub Bot commented on KAFKA-6868: --- hachikuji closed pull request #4980: KAFKA-6868: Fix buffer

[jira] [Commented] (KAFKA-6873) Broker is not returning data including requested offset

[ https://issues.apache.org/jira/browse/KAFKA-6873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482741#comment-16482741 ] Ismael Juma commented on KAFKA-6873: And, as seen here, it's possible that offsets in that batch after

[jira] [Updated] (KAFKA-6868) BufferUnderflowException in client when querying consumer group information

[ https://issues.apache.org/jira/browse/KAFKA-6868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-6868: --- Affects Version/s: (was: 2.0.0) > BufferUnderflowException in client when querying

[jira] [Updated] (KAFKA-6868) BufferUnderflowException in client when querying consumer group information

[ https://issues.apache.org/jira/browse/KAFKA-6868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-6868: --- Fix Version/s: (was: 2.0.0) > BufferUnderflowException in client when querying consumer

[jira] [Commented] (KAFKA-6839) ZK session retry with cname record

[ https://issues.apache.org/jira/browse/KAFKA-6839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482730#comment-16482730 ] Tyler Monahan commented on KAFKA-6839: -- this appears to have fixed the issue for me. Thank you. > ZK

[jira] [Resolved] (KAFKA-6839) ZK session retry with cname record

[ https://issues.apache.org/jira/browse/KAFKA-6839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tyler Monahan resolved KAFKA-6839. -- Resolution: Invalid > ZK session retry with cname record > -- >

[jira] [Updated] (KAFKA-6873) Broker is not returning data including requested offset

[ https://issues.apache.org/jira/browse/KAFKA-6873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-6873: --- Priority: Minor (was: Blocker) > Broker is not returning data including requested offset >

[jira] [Resolved] (KAFKA-6873) Broker is not returning data including requested offset

[ https://issues.apache.org/jira/browse/KAFKA-6873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6873. Resolution: Not A Problem > Broker is not returning data including requested offset >

[jira] [Created] (KAFKA-6926) Reduce NPath exceptions in Connect

Randall Hauch created KAFKA-6926: Summary: Reduce NPath exceptions in Connect Key: KAFKA-6926 URL: https://issues.apache.org/jira/browse/KAFKA-6926 Project: Kafka Issue Type: Improvement

[jira] [Created] (KAFKA-6925) Memory leak in org.apache.kafka.streams.processor.internals.StreamThread$StreamsMetricsThreadImpl

Marcin Kuthan created KAFKA-6925: Summary: Memory leak in org.apache.kafka.streams.processor.internals.StreamThread$StreamsMetricsThreadImpl Key: KAFKA-6925 URL: https://issues.apache.org/jira/browse/KAFKA-6925

[jira] [Updated] (KAFKA-6925) Memory leak in org.apache.kafka.streams.processor.internals.StreamThread$StreamsMetricsThreadImpl

[ https://issues.apache.org/jira/browse/KAFKA-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcin Kuthan updated KAFKA-6925: - Description: The retained heap of 

[jira] [Updated] (KAFKA-6925) Memory leak in org.apache.kafka.streams.processor.internals.StreamThread$StreamsMetricsThreadImpl

[ https://issues.apache.org/jira/browse/KAFKA-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcin Kuthan updated KAFKA-6925: - Description: The retained heap of 

[jira] [Commented] (KAFKA-2951) Additional authorization test cases

[ https://issues.apache.org/jira/browse/KAFKA-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482830#comment-16482830 ] ASF GitHub Bot commented on KAFKA-2951: --- omkreddy opened a new pull request #5054: KAFKA-2951: Add a

[jira] [Commented] (KAFKA-6562) KIP-255: OAuth Authentication via SASL/OAUTHBEARER

[ https://issues.apache.org/jira/browse/KAFKA-6562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482906#comment-16482906 ] Ismael Juma commented on KAFKA-6562: https://github.com/apache/kafka/pull/4994 > KIP-255: OAuth

[jira] [Commented] (KAFKA-6709) broker failed to handle request due to OOM

[ https://issues.apache.org/jira/browse/KAFKA-6709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482916#comment-16482916 ] Ismael Juma commented on KAFKA-6709: https://github.com/apache/kafka/pull/4871 > broker failed to

[jira] [Updated] (KAFKA-6709) broker failed to handle request due to OOM

[ https://issues.apache.org/jira/browse/KAFKA-6709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-6709: --- Fix Version/s: 2.0.0 > broker failed to handle request due to OOM >

[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=16482760#comment-16482760 ] M. Manna commented on KAFKA-6188: - [~lindong]  Hey Dong. Thanks for your valuable comments on the issue. I

[jira] [Updated] (KAFKA-6750) Add listener name to AuthenticationContext

[ https://issues.apache.org/jira/browse/KAFKA-6750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-6750: --- Fix Version/s: 2.0.0 > Add listener name to AuthenticationContext >

[jira] [Commented] (KAFKA-6474) Rewrite test to use new public TopologyTestDriver

[ https://issues.apache.org/jira/browse/KAFKA-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482758#comment-16482758 ] ASF GitHub Bot commented on KAFKA-6474: --- h314to opened a new pull request #5052: KAFKA-6474: Rewrite

[jira] [Updated] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3665: --- Labels: (was: windows) > Default ssl.endpoint.identification.algorithm should be https >

[jira] [Commented] (KAFKA-6629) SegmentedCacheFunctionTest does not cover session window serdes

[ https://issues.apache.org/jira/browse/KAFKA-6629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482819#comment-16482819 ] Manasvi Gupta commented on KAFKA-6629: --  Hi [~vpopov89], I am working on this issue. Thanks

[jira] [Reopened] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reopened KAFKA-3665: > Default ssl.endpoint.identification.algorithm should be https >

[jira] [Resolved] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3665. Resolution: Fixed > Default ssl.endpoint.identification.algorithm should be https >

[jira] [Commented] (KAFKA-6924) Making state store queryable on replicas

[ https://issues.apache.org/jira/browse/KAFKA-6924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483155#comment-16483155 ] Guozhang Wang commented on KAFKA-6924: -- Hello Navinder, thanks for reporting this JIRA. Is it the

[jira] [Commented] (KAFKA-6925) Memory leak in org.apache.kafka.streams.processor.internals.StreamThread$StreamsMetricsThreadImpl

[ https://issues.apache.org/jira/browse/KAFKA-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483158#comment-16483158 ] Guozhang Wang commented on KAFKA-6925: -- This seems to be a known issue that we have fixed in trunk.

[jira] [Commented] (KAFKA-6927) Broker uses significant amount of memory during down-conversion

[ https://issues.apache.org/jira/browse/KAFKA-6927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483063#comment-16483063 ] Dhruvil Shah commented on KAFKA-6927: - [https://github.com/apache/kafka/pull/4871] > Broker uses

[jira] [Created] (KAFKA-6927) Broker uses significant amount of memory during down-conversion

Dhruvil Shah created KAFKA-6927: --- Summary: Broker uses significant amount of memory during down-conversion Key: KAFKA-6927 URL: https://issues.apache.org/jira/browse/KAFKA-6927 Project: Kafka

[jira] [Created] (KAFKA-6928) StreamsPartitionAssignor is double retrying within InternalTopicManager

Guozhang Wang created KAFKA-6928: Summary: StreamsPartitionAssignor is double retrying within InternalTopicManager Key: KAFKA-6928 URL: https://issues.apache.org/jira/browse/KAFKA-6928 Project: Kafka

[jira] [Commented] (KAFKA-2561) Optionally support OpenSSL for SSL/TLS

[ https://issues.apache.org/jira/browse/KAFKA-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483042#comment-16483042 ] Ismael Juma commented on KAFKA-2561: [~prasincs], given the improvement in Java 9, this work seems

[jira] [Commented] (KAFKA-1400) transient unit test failure in SocketServerTest

[ https://issues.apache.org/jira/browse/KAFKA-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483195#comment-16483195 ] ASF GitHub Bot commented on KAFKA-1400: --- JimGalasyn opened a new pull request #142: KAFKA-1400: Fix

[jira] [Commented] (KAFKA-6916) AdminClient does not refresh metadata on broker failure

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

[jira] [Commented] (KAFKA-1400) transient unit test failure in SocketServerTest

[ https://issues.apache.org/jira/browse/KAFKA-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483189#comment-16483189 ] ASF GitHub Bot commented on KAFKA-1400: --- JimGalasyn opened a new pull request #5056: KAFKA-1400: Fix