[jira] [Commented] (KAFKA-7362) enable kafka broker to remove orphan partitions automatically

[ https://issues.apache.org/jira/browse/KAFKA-7362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804577#comment-16804577 ] xiongqi wu commented on KAFKA-7362: --- Yes, I am stilling looking forward on fixing this issue.  I was

[jira] [Commented] (KAFKA-8157) Missing "key.serializer" exception when setting "segment index bytes"

[ https://issues.apache.org/jira/browse/KAFKA-8157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804539#comment-16804539 ] Travis Brad Ellis commented on KAFKA-8157: -- I'd like to work this. Newbie here. I sent a request

[jira] [Commented] (KAFKA-7965) Flaky Test ConsumerBounceTest#testRollingBrokerRestartsWithSmallerMaxGroupSizeConfigDisruptsBigGroup

[ https://issues.apache.org/jira/browse/KAFKA-7965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804533#comment-16804533 ] huxihx commented on KAFKA-7965: --- Part of the failure is caused by the fact that the rebalance did not

[jira] [Commented] (KAFKA-8106) Remove unnecessary decompression operation when logValidator do validation.

[ https://issues.apache.org/jira/browse/KAFKA-8106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804532#comment-16804532 ] hackerwin7 commented on KAFKA-8106: --- Maybe we can put the record level validation to client endpoint or

[jira] [Created] (KAFKA-8174) Can't call arbitrary SimpleBenchmarks tests from streams_simple_benchmark_test.py

Sophie Blee-Goldman created KAFKA-8174: -- Summary: Can't call arbitrary SimpleBenchmarks tests from streams_simple_benchmark_test.py Key: KAFKA-8174 URL: https://issues.apache.org/jira/browse/KAFKA-8174

[jira] [Commented] (KAFKA-7362) enable kafka broker to remove orphan partitions automatically

[ https://issues.apache.org/jira/browse/KAFKA-7362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804470#comment-16804470 ] Dhruvil Shah commented on KAFKA-7362: - [~xiongqiwu] are you planning to work on this JIRA? If not, I

[jira] [Updated] (KAFKA-8159) Built-in serdes for signed numbers do not obey lexicographical ordering

[ https://issues.apache.org/jira/browse/KAFKA-8159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sophie Blee-Goldman updated KAFKA-8159: --- Description: Currently we assume consistent ordering between serialized and

[jira] [Commented] (KAFKA-7502) Cleanup KTable materialization logic in a single place

[ https://issues.apache.org/jira/browse/KAFKA-7502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804456#comment-16804456 ] ASF GitHub Bot commented on KAFKA-7502: --- dongjinleekr commented on pull request #6520: KAFKA-7502:

[jira] [Updated] (KAFKA-8159) Built-in serdes for signed numbers do not obey lexicographical ordering

[ https://issues.apache.org/jira/browse/KAFKA-8159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sophie Blee-Goldman updated KAFKA-8159: --- Summary: Built-in serdes for signed numbers do not obey lexicographical ordering

[jira] [Commented] (KAFKA-7502) Cleanup KTable materialization logic in a single place

[ https://issues.apache.org/jira/browse/KAFKA-7502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804449#comment-16804449 ] ASF GitHub Bot commented on KAFKA-7502: --- dongjinleekr commented on pull request #6519: KAFKA-7502:

[jira] [Updated] (KAFKA-8173) Kafka Errors after version upgrade from 0.10.2.2 to 2.1.1

[ https://issues.apache.org/jira/browse/KAFKA-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amit Anand updated KAFKA-8173: -- Description: After Kafka version upgrade from 0.10.2.2 to 2.1.1 Warnings starts coming for all the

[jira] [Created] (KAFKA-8173) Kafka Errors after version upgrade from 0.10.2.2 to 2.1.1

Amit Anand created KAFKA-8173: - Summary: Kafka Errors after version upgrade from 0.10.2.2 to 2.1.1 Key: KAFKA-8173 URL: https://issues.apache.org/jira/browse/KAFKA-8173 Project: Kafka Issue

[jira] [Commented] (KAFKA-7502) Cleanup KTable materialization logic in a single place

[ https://issues.apache.org/jira/browse/KAFKA-7502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804297#comment-16804297 ] ASF GitHub Bot commented on KAFKA-7502: --- guozhangwang commented on pull request #6453: KAFKA-7502:

[jira] [Updated] (KAFKA-8172) FileSystemException: The process cannot access the file because it is being used by another process

[ https://issues.apache.org/jira/browse/KAFKA-8172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kondeti updated KAFKA-8172: -- Description: Fix to close file handlers before renaming files / directories and open them

[jira] [Commented] (KAFKA-8172) FileSystemException: The process cannot access the file because it is being used by another process

[ https://issues.apache.org/jira/browse/KAFKA-8172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804243#comment-16804243 ] Bharat Kondeti commented on KAFKA-8172: --- Pull request link > FileSystemException: The process

[jira] [Commented] (KAFKA-8172) FileSystemException: The process cannot access the file because it is being used by another process

[ https://issues.apache.org/jira/browse/KAFKA-8172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804235#comment-16804235 ] Bharat Kondeti commented on KAFKA-8172: --- Pull request  > FileSystemException: The process cannot

[jira] [Created] (KAFKA-8172) FileSystemException: The process cannot access the file because it is being used by another process

Bharat Kondeti created KAFKA-8172: - Summary: FileSystemException: The process cannot access the file because it is being used by another process Key: KAFKA-8172 URL:

[jira] [Commented] (KAFKA-6983) Error while deleting segments - The process cannot access the file because it is being used by another process

[ https://issues.apache.org/jira/browse/KAFKA-6983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804224#comment-16804224 ] ASF GitHub Bot commented on KAFKA-6983: --- kondetibharat commented on pull request #6517: KAFKA-6983:

[jira] [Commented] (KAFKA-7895) Ktable supress operator emitting more than one record for the same key per window

[ https://issues.apache.org/jira/browse/KAFKA-7895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804179#comment-16804179 ] John Roesler commented on KAFKA-7895: - Here's the repro I put together. It'll take me a little while

[jira] [Comment Edited] (KAFKA-7895) Ktable supress operator emitting more than one record for the same key per window

[ https://issues.apache.org/jira/browse/KAFKA-7895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804035#comment-16804035 ] John Roesler edited comment on KAFKA-7895 at 3/28/19 6:01 PM: -- EDIT:

[jira] [Commented] (KAFKA-7965) Flaky Test ConsumerBounceTest#testRollingBrokerRestartsWithSmallerMaxGroupSizeConfigDisruptsBigGroup

[ https://issues.apache.org/jira/browse/KAFKA-7965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804148#comment-16804148 ] Guozhang Wang commented on KAFKA-7965: -- [~enether] Saw another failure:

[jira] [Updated] (KAFKA-8171) callback needs to be null when addStopReplicaRequestForBrokers when replica state transits to offline

[ https://issues.apache.org/jira/browse/KAFKA-8171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kehu updated KAFKA-8171: Description: Problem:  In ControllerChannelManager.sendRequestsToBrokers, for STOP_REPLICA requests, it will try

[jira] [Created] (KAFKA-8171) callback needs to be null when addStopReplicaRequestForBrokers when replica state transits to offline

kehu created KAFKA-8171: --- Summary: callback needs to be null when addStopReplicaRequestForBrokers when replica state transits to offline Key: KAFKA-8171 URL: https://issues.apache.org/jira/browse/KAFKA-8171

[jira] [Commented] (KAFKA-7895) Ktable supress operator emitting more than one record for the same key per window

[ https://issues.apache.org/jira/browse/KAFKA-7895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804035#comment-16804035 ] John Roesler commented on KAFKA-7895: - Thanks! Also, can you elaborate on how

[jira] [Commented] (KAFKA-7981) Add Replica Fetcher and Log Cleaner Count Metrics

[ https://issues.apache.org/jira/browse/KAFKA-7981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804012#comment-16804012 ] ASF GitHub Bot commented on KAFKA-7981: --- viktorsomogyi commented on pull request #6514: KAFKA-7981:

[jira] [Commented] (KAFKA-8106) Remove unnecessary decompression operation when logValidator do validation.

[ https://issues.apache.org/jira/browse/KAFKA-8106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804003#comment-16804003 ] hackerwin7 commented on KAFKA-8106: --- The `validateRecord()` is placed in every branch of

[jira] [Commented] (KAFKA-8103) Kafka SIGSEGV on kafka-network-thread

[ https://issues.apache.org/jira/browse/KAFKA-8103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16803955#comment-16803955 ] Ismael Juma commented on KAFKA-8103: Looks like a JVM JIT bug. I haven't seen this one before, so I

[jira] [Commented] (KAFKA-8170) To add kafka data at rest encryption

[ https://issues.apache.org/jira/browse/KAFKA-8170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16803940#comment-16803940 ] Sönke Liebau commented on KAFKA-8170: - Hi [~ashelke],  I've proposed

[jira] [Commented] (KAFKA-8103) Kafka SIGSEGV on kafka-network-thread

[ https://issues.apache.org/jira/browse/KAFKA-8103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16803933#comment-16803933 ] Sean Humbarger commented on KAFKA-8103: --- We are still seeing random JVM crashes.  We've switched

[jira] [Created] (KAFKA-8170) To add kafka data at rest encryption

Akash created KAFKA-8170: Summary: To add kafka data at rest encryption Key: KAFKA-8170 URL: https://issues.apache.org/jira/browse/KAFKA-8170 Project: Kafka Issue Type: New Feature

[jira] [Commented] (KAFKA-7895) Ktable supress operator emitting more than one record for the same key per window

[ https://issues.apache.org/jira/browse/KAFKA-7895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16803813#comment-16803813 ] Andrew Klopper commented on KAFKA-7895: --- Hi John Roesler Yes, my consumer's isolation level is set

[jira] [Updated] (KAFKA-8165) Streams task causes Out Of Memory after connection issues and store restoration

[ https://issues.apache.org/jira/browse/KAFKA-8165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Campo updated KAFKA-8165: Description: Having a Kafka Streams 2.1 application, when Kafka brokers are stable, the (largely

[jira] [Updated] (KAFKA-8165) Streams task causes Out Of Memory after connection issues and store restoration

[ https://issues.apache.org/jira/browse/KAFKA-8165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Campo updated KAFKA-8165: Environment: 3 nodes, 22 topics, 16 partitions per topic, 1 window store, 4 KV stores. Kafka Streams

[jira] [Commented] (KAFKA-8169) Wrong topic on streams quick start documentation

[ https://issues.apache.org/jira/browse/KAFKA-8169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16803656#comment-16803656 ] Tcheutchoua Steve commented on KAFKA-8169: -- This has been adjusted and patched in this

[jira] [Created] (KAFKA-8169) Wrong topic on streams quick start documentation

Tcheutchoua Steve created KAFKA-8169: Summary: Wrong topic on streams quick start documentation Key: KAFKA-8169 URL: https://issues.apache.org/jira/browse/KAFKA-8169 Project: Kafka Issue

[jira] [Commented] (KAFKA-6042) Kafka Request Handler deadlocks and brings down the cluster.

[ https://issues.apache.org/jira/browse/KAFKA-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16803630#comment-16803630 ] Ismael Juma commented on KAFKA-6042: Fixed. > Kafka Request Handler deadlocks and brings down the

[jira] [Updated] (KAFKA-6042) Kafka Request Handler deadlocks and brings down the cluster.

[ https://issues.apache.org/jira/browse/KAFKA-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-6042: --- Affects Version/s: (was: 1.0.0) > Kafka Request Handler deadlocks and brings down the cluster. >