[jira] [Created] (KAFKA-8537) Kafka issues after 2.1.0 upgrade: java.net.SocketTimeoutException: Failed to connect within 30000 ms

2019-06-13 Thread VinayKumar (JIRA)
VinayKumar created KAFKA-8537: - Summary: Kafka issues after 2.1.0 upgrade: java.net.SocketTimeoutException: Failed to connect within 3 ms Key: KAFKA-8537 URL: https://issues.apache.org/jira/browse/KAFKA-8537

[jira] [Commented] (KAFKA-7870) Error sending fetch request (sessionId=1578860481, epoch=INITIAL) to node 2: java.io.IOException: Connection to 2 was disconnected before the response was read.

2019-12-07 Thread VinayKumar (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16990592#comment-16990592 ] VinayKumar commented on KAFKA-7870: --- As mentioned by [~ayusman] in the above comment, i

[jira] [Commented] (KAFKA-7697) Possible deadlock in kafka.cluster.Partition

2019-12-07 Thread VinayKumar (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-7697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16990593#comment-16990593 ] VinayKumar commented on KAFKA-7697: --- Does increasing num.network.threads help improve t

[jira] [Created] (KAFKA-8916) Unreliable kafka-reassign-partitions.sh affecting performance

2019-09-17 Thread VinayKumar (Jira)
VinayKumar created KAFKA-8916: - Summary: Unreliable kafka-reassign-partitions.sh affecting performance Key: KAFKA-8916 URL: https://issues.apache.org/jira/browse/KAFKA-8916 Project: Kafka Issue

[jira] [Created] (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 invalid

2017-11-23 Thread VinayKumar (JIRA)
VinayKumar created KAFKA-6266: - Summary: 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 invalid. (kafka.log.LogCleanerManager$)

[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

2017-11-23 Thread VinayKumar (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16264653#comment-16264653 ] VinayKumar commented on KAFKA-6266: --- Thank you for the reply. The errors don't go away,

[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

2017-11-30 Thread VinayKumar (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16272553#comment-16272553 ] VinayKumar commented on KAFKA-6266: --- Hi, The log.cleanup.policy is 'delete' log.cleanup

[jira] [Created] (KAFKA-6305) log.retention.hours, retention.ms not working in segments deletion for kafka topic

2017-12-03 Thread VinayKumar (JIRA)
VinayKumar created KAFKA-6305: - Summary: log.retention.hours, retention.ms not working in segments deletion for kafka topic Key: KAFKA-6305 URL: https://issues.apache.org/jira/browse/KAFKA-6305 Project: K

[jira] [Created] (KAFKA-6315) kafka-console-consumer.sh terminating consumer process only for one partition with java.lang.IllegalArgumentException: Unknown compression type id: 5

2017-12-06 Thread VinayKumar (JIRA)
VinayKumar created KAFKA-6315: - Summary: kafka-console-consumer.sh terminating consumer process only for one partition with java.lang.IllegalArgumentException: Unknown compression type id: 5 Key: KAFKA-6315 URL: http

[jira] [Commented] (KAFKA-7870) Error sending fetch request (sessionId=1578860481, epoch=INITIAL) to node 2: java.io.IOException: Connection to 2 was disconnected before the response was read.

2020-07-15 Thread VinayKumar (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17158850#comment-17158850 ] VinayKumar commented on KAFKA-7870: --- The same issue is seen in 2.4.1 version also. Can

[jira] [Created] (KAFKA-6458) ERROR Found invalid messages during fetch for partition [__consumer_offsets,20] offset 0 error Record is corrupt (stored crc = 73, computed crc = 2559213387) (kafka.serve

2018-01-17 Thread VinayKumar (JIRA)
VinayKumar created KAFKA-6458: - Summary: ERROR Found invalid messages during fetch for partition [__consumer_offsets,20] offset 0 error Record is corrupt (stored crc = 73, computed crc = 2559213387) (kafka.server.ReplicaFetcherThread)

[jira] [Created] (KAFKA-6801) Restrict Consumer to fetch data from secure port only, and deny from non-secure port.

2018-04-18 Thread VinayKumar (JIRA)
VinayKumar created KAFKA-6801: - Summary: Restrict Consumer to fetch data from secure port only, and deny from non-secure port. Key: KAFKA-6801 URL: https://issues.apache.org/jira/browse/KAFKA-6801 Project