[jira] [Resolved] (KAFKA-15041) Source Connector auto topic creation fails when topic is deleted and brokers don't support auto topic creation

[ https://issues.apache.org/jira/browse/KAFKA-15041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao resolved KAFKA-15041. --- Resolution: Won't Fix For now, setting the config `producer.override.max.block.ms` at a connector

[jira] [Updated] (KAFKA-14401) Connector/Tasks reading offsets can get stuck if underneath WorkThread dies

[ https://issues.apache.org/jira/browse/KAFKA-14401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao updated KAFKA-14401: -- Description: When a connector or task tries to read the offsets from the offsets topic, it issues

[jira] [Updated] (KAFKA-14401) Connector/Tasks reading offsets can get stuck if underneath WorkThread dies

[ https://issues.apache.org/jira/browse/KAFKA-14401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao updated KAFKA-14401: -- Description: When a connector or task tries to read the offsets from the offsets topic, it issues

[jira] [Commented] (KAFKA-16604) Deprecate ConfigDef.ConfigKey constructor from public APIs

[ https://issues.apache.org/jira/browse/KAFKA-16604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17840163#comment-17840163 ] Sagar Rao commented on KAFKA-16604: --- [~chia7712] , ok i have assigned it to myself. > Deprecate

[jira] [Assigned] (KAFKA-16604) Deprecate ConfigDef.ConfigKey constructor from public APIs

[ https://issues.apache.org/jira/browse/KAFKA-16604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao reassigned KAFKA-16604: - Assignee: Sagar Rao > Deprecate ConfigDef.ConfigKey constructor from public APIs >

[jira] [Created] (KAFKA-16604) Deprecate ConfigDef.ConfigKey constructor from public APIs

Sagar Rao created KAFKA-16604: - Summary: Deprecate ConfigDef.ConfigKey constructor from public APIs Key: KAFKA-16604 URL: https://issues.apache.org/jira/browse/KAFKA-16604 Project: Kafka Issue

[jira] [Created] (KAFKA-16592) ConfigKey constructor update can break clients using it

Sagar Rao created KAFKA-16592: - Summary: ConfigKey constructor update can break clients using it Key: KAFKA-16592 URL: https://issues.apache.org/jira/browse/KAFKA-16592 Project: Kafka Issue

[jira] [Comment Edited] (KAFKA-16578) Revert changes to connect_distributed_test.py for the new async Consumer

[ https://issues.apache.org/jira/browse/KAFKA-16578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838609#comment-17838609 ] Sagar Rao edited comment on KAFKA-16578 at 4/18/24 3:02 PM: [~kirktrue], I

[jira] [Comment Edited] (KAFKA-16578) Revert changes to connect_distributed_test.py for the new async Consumer

[ https://issues.apache.org/jira/browse/KAFKA-16578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838609#comment-17838609 ] Sagar Rao edited comment on KAFKA-16578 at 4/18/24 11:11 AM: - [~kirktrue], I

[jira] [Comment Edited] (KAFKA-16578) Revert changes to connect_distributed_test.py for the new async Consumer

[ https://issues.apache.org/jira/browse/KAFKA-16578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838609#comment-17838609 ] Sagar Rao edited comment on KAFKA-16578 at 4/18/24 11:10 AM: - [~kirktrue], I

[jira] [Commented] (KAFKA-16578) Revert changes to connect_distributed_test.py for the new async Consumer

[ https://issues.apache.org/jira/browse/KAFKA-16578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838609#comment-17838609 ] Sagar Rao commented on KAFKA-16578: --- [~kirktrue], I am working on modifying the the system tests for

[jira] [Assigned] (KAFKA-16481) Fix flaky kafka.server.ReplicaManagerTest#testRemoteLogReaderMetrics

[ https://issues.apache.org/jira/browse/KAFKA-16481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao reassigned KAFKA-16481: - Assignee: Sagar Rao > Fix flaky kafka.server.ReplicaManagerTest#testRemoteLogReaderMetrics >

[jira] [Commented] (KAFKA-16272) Update connect_distributed_test.py to support KIP-848’s group protocol config

[ https://issues.apache.org/jira/browse/KAFKA-16272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832894#comment-17832894 ] Sagar Rao commented on KAFKA-16272: --- [~kirktrue], thanks I chnged the status to In Progress > Update

[jira] [Assigned] (KAFKA-16272) Update connect_distributed_test.py to support KIP-848’s group protocol config

[ https://issues.apache.org/jira/browse/KAFKA-16272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao reassigned KAFKA-16272: - Assignee: Sagar Rao > Update connect_distributed_test.py to support KIP-848’s group protocol

[jira] [Updated] (KAFKA-16197) Connect Worker poll timeout prints Consumer poll timeout specific warnings.

[ https://issues.apache.org/jira/browse/KAFKA-16197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao updated KAFKA-16197: -- Description: When a Connect worker's poll timeout expires in Connect, the log lines that we see are:

[jira] [Updated] (KAFKA-16197) Connect Worker poll timeout prints Consumer poll timeout specific warnings.

[ https://issues.apache.org/jira/browse/KAFKA-16197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao updated KAFKA-16197: -- Component/s: connect > Connect Worker poll timeout prints Consumer poll timeout specific warnings. >

[jira] [Created] (KAFKA-16197) Connect Worker poll timeout prints Consumer poll timeout specific warnings.

Sagar Rao created KAFKA-16197: - Summary: Connect Worker poll timeout prints Consumer poll timeout specific warnings. Key: KAFKA-16197 URL: https://issues.apache.org/jira/browse/KAFKA-16197 Project: Kafka

[jira] [Updated] (KAFKA-16039) RecordHeaders supports the addAll method

[ https://issues.apache.org/jira/browse/KAFKA-16039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao updated KAFKA-16039: -- Labels: need-kip (was: ) > RecordHeaders supports the addAll method >

[jira] [Created] (KAFKA-16056) Worker poll timeout expiry can lead to Duplicate task assignments.

Sagar Rao created KAFKA-16056: - Summary: Worker poll timeout expiry can lead to Duplicate task assignments. Key: KAFKA-16056 URL: https://issues.apache.org/jira/browse/KAFKA-16056 Project: Kafka

[jira] [Commented] (KAFKA-14454) KTableKTableForeignKeyInnerJoinCustomPartitionerIntegrationTest#shouldThrowIllegalArgumentExceptionWhenCustomPartionerReturnsMultiplePartitions passes when run individ

[ https://issues.apache.org/jira/browse/KAFKA-14454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796108#comment-17796108 ] Sagar Rao commented on KAFKA-14454: --- Aah ok, no problem at all :) Good to know that it worked and that

[jira] [Commented] (KAFKA-14454) KTableKTableForeignKeyInnerJoinCustomPartitionerIntegrationTest#shouldThrowIllegalArgumentExceptionWhenCustomPartionerReturnsMultiplePartitions passes when run individ

[ https://issues.apache.org/jira/browse/KAFKA-14454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796095#comment-17796095 ] Sagar Rao commented on KAFKA-14454: --- [~cadonna], I don't recall the error and I tried to find the

[jira] [Commented] (KAFKA-10873) Inaccurate "Ignoring stop request for unowned connector" log messages

[ https://issues.apache.org/jira/browse/KAFKA-10873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787561#comment-17787561 ] Sagar Rao commented on KAFKA-10873: --- FWIW, we hit a scenario today where the same sequence of logs

[jira] [Commented] (KAFKA-15770) org.apache.kafka.streams.integration.ConsistencyVectorIntegrationTest.shouldHaveSamePositionBoundActiveAndStandBy is flaky

[ https://issues.apache.org/jira/browse/KAFKA-15770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17786693#comment-17786693 ] Sagar Rao commented on KAFKA-15770: --- Noticed an instance here:

[jira] [Commented] (KAFKA-15687) Update host address for the GoupMetadata when replace static members

[ https://issues.apache.org/jira/browse/KAFKA-15687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779863#comment-17779863 ] Sagar Rao commented on KAFKA-15687: --- Thanks for filing this bug [~LucentWong]. You have pointed to the

[jira] [Commented] (KAFKA-13152) Replace "buffered.records.per.partition" & "cache.max.bytes.buffering" with "{statestore.cache}/{input.buffer}.max.bytes"

[ https://issues.apache.org/jira/browse/KAFKA-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779839#comment-17779839 ] Sagar Rao commented on KAFKA-13152: --- Thanks [~ableegoldman], there are merge conflicts which need

[jira] [Assigned] (KAFKA-13976) Improvements for OpenAPI specs

[ https://issues.apache.org/jira/browse/KAFKA-13976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao reassigned KAFKA-13976: - Assignee: (was: Sagar Rao) > Improvements for OpenAPI specs >

[jira] [Assigned] (KAFKA-15237) Implement write operation timeout

[ https://issues.apache.org/jira/browse/KAFKA-15237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao reassigned KAFKA-15237: - Assignee: Sagar Rao (was: David Jacot) > Implement write operation timeout >

[jira] [Assigned] (KAFKA-15454) Add support for OffsetCommit version 9 in admin client

[ https://issues.apache.org/jira/browse/KAFKA-15454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao reassigned KAFKA-15454: - Assignee: Sagar Rao > Add support for OffsetCommit version 9 in admin client >

[jira] [Assigned] (KAFKA-15457) Add support for OffsetFetch version 9 in admin

[ https://issues.apache.org/jira/browse/KAFKA-15457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao reassigned KAFKA-15457: - Assignee: Sagar Rao > Add support for OffsetFetch version 9 in admin >

[jira] [Commented] (KAFKA-13152) Replace "buffered.records.per.partition" & "cache.max.bytes.buffering" with "{statestore.cache}/{input.buffer}.max.bytes"

[ https://issues.apache.org/jira/browse/KAFKA-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17775716#comment-17775716 ] Sagar Rao commented on KAFKA-13152: --- Makes sense Stanislav! If we can have experts from Streams to

[jira] [Commented] (KAFKA-13152) Replace "buffered.records.per.partition" & "cache.max.bytes.buffering" with "{statestore.cache}/{input.buffer}.max.bytes"

[ https://issues.apache.org/jira/browse/KAFKA-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17775701#comment-17775701 ] Sagar Rao commented on KAFKA-13152: --- [~enether], that's correct.. the reviews are pending for this. I

[jira] [Comment Edited] (KAFKA-13152) Replace "buffered.records.per.partition" & "cache.max.bytes.buffering" with "{statestore.cache}/{input.buffer}.max.bytes"

[ https://issues.apache.org/jira/browse/KAFKA-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17775701#comment-17775701 ] Sagar Rao edited comment on KAFKA-13152 at 10/16/23 11:15 AM: -- [~enether],

[jira] [Commented] (KAFKA-15020) integration.kafka.server.FetchFromFollowerIntegrationTest.testRackAwareRangeAssignor test is flaky

[ https://issues.apache.org/jira/browse/KAFKA-15020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17772105#comment-17772105 ] Sagar Rao commented on KAFKA-15020: --- I found the original stacktrace is showing up in one of the

[jira] [Assigned] (KAFKA-14516) Implement static membeship

[ https://issues.apache.org/jira/browse/KAFKA-14516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao reassigned KAFKA-14516: - Assignee: Sagar Rao (was: David Jacot) > Implement static membeship >

[jira] [Commented] (KAFKA-14516) Implement static membeship

[ https://issues.apache.org/jira/browse/KAFKA-14516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767939#comment-17767939 ] Sagar Rao commented on KAFKA-14516: --- [~dajac], sure , thank you very much! > Implement static

[jira] [Commented] (KAFKA-14504) Implement DescribeGroups API

[ https://issues.apache.org/jira/browse/KAFKA-14504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767925#comment-17767925 ] Sagar Rao commented on KAFKA-14504: --- Sure, I would be happy to help :) > Implement DescribeGroups

[jira] [Comment Edited] (KAFKA-14504) Implement DescribeGroups API

[ https://issues.apache.org/jira/browse/KAFKA-14504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767920#comment-17767920 ] Sagar Rao edited comment on KAFKA-14504 at 9/22/23 9:23 AM: [~dajac], is it

[jira] [Commented] (KAFKA-14504) Implement DescribeGroups API

[ https://issues.apache.org/jira/browse/KAFKA-14504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767920#comment-17767920 ] Sagar Rao commented on KAFKA-14504: --- [~dajac], is it still too urgent? I can take a stab at it if it's

[jira] [Commented] (KAFKA-15460) Add group type filter to ListGroups API

[ https://issues.apache.org/jira/browse/KAFKA-15460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767900#comment-17767900 ] Sagar Rao commented on KAFKA-15460: --- [~zhaohaidao]are you currently working on this? > Add group

[jira] [Comment Edited] (KAFKA-15473) Connect connector-plugins endpoint shows duplicate plugins

[ https://issues.apache.org/jira/browse/KAFKA-15473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17766738#comment-17766738 ] Sagar Rao edited comment on KAFKA-15473 at 9/19/23 10:33 AM: -

[jira] [Commented] (KAFKA-15473) Connect connector-plugins endpoint shows duplicate plugins

[ https://issues.apache.org/jira/browse/KAFKA-15473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17766738#comment-17766738 ] Sagar Rao commented on KAFKA-15473: --- [~satish.duggana], No the API documentation doesn't mention

[jira] (KAFKA-14401) Connector/Tasks reading offsets can get stuck if underneath WorkThread dies

[ https://issues.apache.org/jira/browse/KAFKA-14401 ] Sagar Rao deleted comment on KAFKA-14401: --- was (Author: sagarrao): There are a couple of routes that can be taken here:   1) As discussed, we try to reinitiate the WorkThread in case the

[jira] [Assigned] (KAFKA-14401) Connector/Tasks reading offsets can get stuck if underneath WorkThread dies

[ https://issues.apache.org/jira/browse/KAFKA-14401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao reassigned KAFKA-14401: - Assignee: Sagar Rao (was: Chaitanya Mukka) > Connector/Tasks reading offsets can get stuck if

[jira] [Updated] (KAFKA-14401) Connector/Tasks reading offsets can get stuck if underneath WorkThread dies

[ https://issues.apache.org/jira/browse/KAFKA-14401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao updated KAFKA-14401: -- Description: When a connector or task tries to read the offsets from the offsets topic, it issues

[jira] [Commented] (KAFKA-15408) Restart failed tasks in Kafka Connect up to a configurable max-tries

[ https://issues.apache.org/jira/browse/KAFKA-15408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17759648#comment-17759648 ] Sagar Rao commented on KAFKA-15408: --- Hi, the steps are outline here:

[jira] [Updated] (KAFKA-15408) Restart failed tasks in Kafka Connect up to a configurable max-tries

[ https://issues.apache.org/jira/browse/KAFKA-15408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao updated KAFKA-15408: -- Labels: needs-kip (was: ) > Restart failed tasks in Kafka Connect up to a configurable max-tries >

[jira] [Commented] (KAFKA-15408) Restart failed tasks in Kafka Connect up to a configurable max-tries

[ https://issues.apache.org/jira/browse/KAFKA-15408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17759529#comment-17759529 ] Sagar Rao commented on KAFKA-15408: --- [~patrickpang], thanks for filing this ! IMO, this is a feature

[jira] [Commented] (KAFKA-14429) Move OffsetStorageReader from storage package to source package

[ https://issues.apache.org/jira/browse/KAFKA-14429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17756308#comment-17756308 ] Sagar Rao commented on KAFKA-14429: --- hey [~gharris1727], given Chris's comment above, do you think we

[jira] [Assigned] (KAFKA-14138) The Exception Throwing Behavior of Transactional Producer is Inconsistent

[ https://issues.apache.org/jira/browse/KAFKA-14138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao reassigned KAFKA-14138: - Assignee: (was: Sagar Rao) > The Exception Throwing Behavior of Transactional Producer is

[jira] [Comment Edited] (KAFKA-15339) Transient I/O error happening in appending records could lead to the halt of whole cluster

[ https://issues.apache.org/jira/browse/KAFKA-15339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755812#comment-17755812 ] Sagar Rao edited comment on KAFKA-15339 at 8/18/23 5:52 AM: Thanks for

[jira] [Commented] (KAFKA-15339) Transient I/O error happening in appending records could lead to the halt of whole cluster

[ https://issues.apache.org/jira/browse/KAFKA-15339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755812#comment-17755812 ] Sagar Rao commented on KAFKA-15339: --- Thanks for reporting this bug [~functioner]. As you correctly

[jira] [Commented] (KAFKA-15354) Partition leader is not evenly distributed in kraft mode

[ https://issues.apache.org/jira/browse/KAFKA-15354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755805#comment-17755805 ] Sagar Rao commented on KAFKA-15354: --- [~dengziming], I took a look at this. I believe this is happening

[jira] [Commented] (KAFKA-15334) DescribeQuorum should not be seen as cluster action

[ https://issues.apache.org/jira/browse/KAFKA-15334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753575#comment-17753575 ] Sagar Rao commented on KAFKA-15334: --- hey [~dengziming] if it isn't too critical, can I take a stab at

[jira] [Created] (KAFKA-15296) Allow committing offsets for Dropped records via SMTs

Sagar Rao created KAFKA-15296: - Summary: Allow committing offsets for Dropped records via SMTs Key: KAFKA-15296 URL: https://issues.apache.org/jira/browse/KAFKA-15296 Project: Kafka Issue Type:

[jira] [Updated] (KAFKA-15229) Increase default value of task.shutdown.graceful.timeout.ms

[ https://issues.apache.org/jira/browse/KAFKA-15229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao updated KAFKA-15229: -- Description: The Kafka Connect config [task.shutdown.graceful.timeout.ms.

[jira] [Updated] (KAFKA-15229) Increase default value of task.shutdown.graceful.timeout.ms

[ https://issues.apache.org/jira/browse/KAFKA-15229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao updated KAFKA-15229: -- Description: The Kafka Connect config [task.shutdown.graceful.timeout.ms.

[jira] [Updated] (KAFKA-15229) Increase default value of task.shutdown.graceful.timeout.ms

[ https://issues.apache.org/jira/browse/KAFKA-15229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao updated KAFKA-15229: -- Labels: (was: needs-kip) > Increase default value of task.shutdown.graceful.timeout.ms >

[jira] [Commented] (KAFKA-10457) JsonConverter.toConnectData trims BigInteger to Long for schema-less case

[ https://issues.apache.org/jira/browse/KAFKA-10457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17746881#comment-17746881 ] Sagar Rao commented on KAFKA-10457: --- Thanks Yash. Yeah probably due to the workaround it hasn't

[jira] [Commented] (KAFKA-15005) Status of KafkaConnect task not correct

[ https://issues.apache.org/jira/browse/KAFKA-15005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17746774#comment-17746774 ] Sagar Rao commented on KAFKA-15005: --- [~LucentWong], the PR for

[jira] [Resolved] (KAFKA-15005) Status of KafkaConnect task not correct

[ https://issues.apache.org/jira/browse/KAFKA-15005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao resolved KAFKA-15005. --- Resolution: Duplicate > Status of KafkaConnect task not correct >

[jira] [Commented] (KAFKA-15239) producerPerformance system test for old client failed after v3.5.0

[ https://issues.apache.org/jira/browse/KAFKA-15239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17746253#comment-17746253 ] Sagar Rao commented on KAFKA-15239: --- [~showuon], I beleive we have this tool migration guideline :

[jira] [Commented] (KAFKA-10457) JsonConverter.toConnectData trims BigInteger to Long for schema-less case

[ https://issues.apache.org/jira/browse/KAFKA-10457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17746198#comment-17746198 ] Sagar Rao commented on KAFKA-10457: --- [~yash.mayya], IIRC, you had worked on an issue related to data

[jira] [Comment Edited] (KAFKA-12283) Flaky Test RebalanceSourceConnectorsIntegrationTest#testMultipleWorkersRejoining

[ https://issues.apache.org/jira/browse/KAFKA-12283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17746197#comment-17746197 ] Sagar Rao edited comment on KAFKA-12283 at 7/24/23 5:02 AM: The flakiness

[jira] [Resolved] (KAFKA-12283) Flaky Test RebalanceSourceConnectorsIntegrationTest#testMultipleWorkersRejoining

[ https://issues.apache.org/jira/browse/KAFKA-12283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao resolved KAFKA-12283. --- Resolution: Fixed > Flaky Test >

[jira] [Commented] (KAFKA-12283) Flaky Test RebalanceSourceConnectorsIntegrationTest#testMultipleWorkersRejoining

[ https://issues.apache.org/jira/browse/KAFKA-12283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17746197#comment-17746197 ] Sagar Rao commented on KAFKA-12283: --- The flakiness with this test was also fixed as part of this PR=>

[jira] [Resolved] (KAFKA-8391) Flaky Test RebalanceSourceConnectorsIntegrationTest#testDeleteConnector

[ https://issues.apache.org/jira/browse/KAFKA-8391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao resolved KAFKA-8391. -- Resolution: Fixed Fixed with https://github.com/apache/kafka/pull/12561 > Flaky Test

[jira] [Comment Edited] (KAFKA-8391) Flaky Test RebalanceSourceConnectorsIntegrationTest#testDeleteConnector

[ https://issues.apache.org/jira/browse/KAFKA-8391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17746195#comment-17746195 ] Sagar Rao edited comment on KAFKA-8391 at 7/24/23 5:00 AM: --- Just bumped upon

[jira] [Commented] (KAFKA-8391) Flaky Test RebalanceSourceConnectorsIntegrationTest#testDeleteConnector

[ https://issues.apache.org/jira/browse/KAFKA-8391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17746195#comment-17746195 ] Sagar Rao commented on KAFKA-8391: -- Just bumped upon this. The issue mentioned above

[jira] [Assigned] (KAFKA-8391) Flaky Test RebalanceSourceConnectorsIntegrationTest#testDeleteConnector

[ https://issues.apache.org/jira/browse/KAFKA-8391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao reassigned KAFKA-8391: Assignee: Sagar Rao > Flaky Test RebalanceSourceConnectorsIntegrationTest#testDeleteConnector >

[jira] [Updated] (KAFKA-15229) Increase default value of task.shutdown.graceful.timeout.ms

[ https://issues.apache.org/jira/browse/KAFKA-15229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao updated KAFKA-15229: -- Description: The Kafka Connect config [task.shutdown.graceful.timeout.ms.

[jira] [Updated] (KAFKA-15229) Increase default value of task.shutdown.graceful.timeout.ms

[ https://issues.apache.org/jira/browse/KAFKA-15229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao updated KAFKA-15229: -- Description: The Kafka Connect config [task.shutdown.graceful.timeout.ms.

[jira] [Created] (KAFKA-15229) Increase default value of task.shutdown.graceful.timeout.ms

Sagar Rao created KAFKA-15229: - Summary: Increase default value of task.shutdown.graceful.timeout.ms Key: KAFKA-15229 URL: https://issues.apache.org/jira/browse/KAFKA-15229 Project: Kafka Issue

[jira] [Assigned] (KAFKA-15218) NPE will be thrown while deleting topic and fetch from follower concurrently

[ https://issues.apache.org/jira/browse/KAFKA-15218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao reassigned KAFKA-15218: - Assignee: Sagar Rao > NPE will be thrown while deleting topic and fetch from follower

[jira] [Resolved] (KAFKA-12525) Inaccurate task status due to status record interleaving in fast rebalances in Connect

[ https://issues.apache.org/jira/browse/KAFKA-12525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao resolved KAFKA-12525. --- Resolution: Fixed > Inaccurate task status due to status record interleaving in fast rebalances >

[jira] [Updated] (KAFKA-15127) Allow offsets to be reset at the same time a connector is deleted.

[ https://issues.apache.org/jira/browse/KAFKA-15127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao updated KAFKA-15127: -- Description: This has been listed as [Future

[jira] [Assigned] (KAFKA-15127) Allow offsets to be reset at the same time a connector is deleted.

[ https://issues.apache.org/jira/browse/KAFKA-15127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao reassigned KAFKA-15127: - Assignee: (was: Sagar Rao) > Allow offsets to be reset at the same time a connector is

[jira] [Commented] (KAFKA-15127) Allow offsets to be reset at the same time a connector is deleted.

[ https://issues.apache.org/jira/browse/KAFKA-15127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17738704#comment-17738704 ] Sagar Rao commented on KAFKA-15127: --- I don't intend working on this immediately or in the near future.

[jira] [Assigned] (KAFKA-15127) Allow offsets to be reset at the same time a connector is deleted.

[ https://issues.apache.org/jira/browse/KAFKA-15127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao reassigned KAFKA-15127: - Assignee: Sagar Rao > Allow offsets to be reset at the same time a connector is deleted. >

[jira] [Created] (KAFKA-15127) Allow offsets to be reset at the same time a connector is deleted.

Sagar Rao created KAFKA-15127: - Summary: Allow offsets to be reset at the same time a connector is deleted. Key: KAFKA-15127 URL: https://issues.apache.org/jira/browse/KAFKA-15127 Project: Kafka

[jira] [Resolved] (KAFKA-14913) Migrate DistributedHerder Executor shutdown to use ThreadUtils#shutdownExecutorServiceQuietly

[ https://issues.apache.org/jira/browse/KAFKA-14913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao resolved KAFKA-14913. --- Resolution: Fixed > Migrate DistributedHerder Executor shutdown to use >

[jira] [Commented] (KAFKA-14913) Migrate DistributedHerder Executor shutdown to use ThreadUtils#shutdownExecutorServiceQuietly

[ https://issues.apache.org/jira/browse/KAFKA-14913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17733859#comment-17733859 ] Sagar Rao commented on KAFKA-14913: --- [~elkkhan] , the PR for this fix is already merged.

[jira] [Assigned] (KAFKA-14131) KafkaBasedLog#readToLogEnd() may accciedently falls into infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-14131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao reassigned KAFKA-14131: - Assignee: Sambhav Jain (was: Sagar Rao) > KafkaBasedLog#readToLogEnd() may accciedently falls

[jira] [Updated] (KAFKA-15041) Source Connector auto topic creation fails when topic is deleted and brokers don't support auto topic creation

[ https://issues.apache.org/jira/browse/KAFKA-15041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao updated KAFKA-15041: -- Description:

[jira] [Updated] (KAFKA-15041) Source Connector auto topic creation fails when topic is deleted and brokers don't support auto topic creation

[ https://issues.apache.org/jira/browse/KAFKA-15041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao updated KAFKA-15041: -- Description:

[jira] [Commented] (KAFKA-15041) Source Connector auto topic creation fails when topic is deleted and brokers don't support auto topic creation

[ https://issues.apache.org/jira/browse/KAFKA-15041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727894#comment-17727894 ] Sagar Rao commented on KAFKA-15041: --- Ideally a worker restart should fix this but it didn't quite

[jira] [Created] (KAFKA-15041) Source Connector auto topic creation fails when topic is deleted and brokers don't support auto topic creation

Sagar Rao created KAFKA-15041: - Summary: Source Connector auto topic creation fails when topic is deleted and brokers don't support auto topic creation Key: KAFKA-15041 URL:

[jira] [Commented] (KAFKA-15018) Potential tombstone offsets corruption for exactly-once source connectors

[ https://issues.apache.org/jira/browse/KAFKA-15018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727444#comment-17727444 ] Sagar Rao commented on KAFKA-15018: --- Thanks [~yash.mayya] . I have assigned this to myself. I went

[jira] [Assigned] (KAFKA-15018) Potential tombstone offsets corruption for exactly-once source connectors

[ https://issues.apache.org/jira/browse/KAFKA-15018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao reassigned KAFKA-15018: - Assignee: Sagar Rao > Potential tombstone offsets corruption for exactly-once source

[jira] [Commented] (KAFKA-15005) Status of KafkaConnect task not correct

[ https://issues.apache.org/jira/browse/KAFKA-15005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17724615#comment-17724615 ] Sagar Rao commented on KAFKA-15005: --- Thank you [~LucentWong] , I have updated the condition in the PR

[jira] [Commented] (KAFKA-15005) Status of KafkaConnect task not correct

[ https://issues.apache.org/jira/browse/KAFKA-15005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17724481#comment-17724481 ] Sagar Rao commented on KAFKA-15005: --- Thanks for the comment [~LucentWong] . Yeah in that PR, I had

[jira] [Commented] (KAFKA-15005) Status of KafkaConnect task not correct

[ https://issues.apache.org/jira/browse/KAFKA-15005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17723885#comment-17723885 ] Sagar Rao commented on KAFKA-15005: --- hey [~LucentWong] thanks for reporting this. This looks very

[jira] [Assigned] (KAFKA-13109) WorkerSourceTask is not enforcing the errors.retry.timeout and errors.retry.delay.max.ms parameters in case of a RetriableException during task.poll()

[ https://issues.apache.org/jira/browse/KAFKA-13109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao reassigned KAFKA-13109: - Assignee: Sagar Rao > WorkerSourceTask is not enforcing the errors.retry.timeout and >

[jira] [Commented] (KAFKA-13156) KafkaStatusBackingStore making incorrect assumption about order of task and connector delete events

[ https://issues.apache.org/jira/browse/KAFKA-13156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722367#comment-17722367 ] Sagar Rao commented on KAFKA-13156: --- hey [~ChrisEgerton] , I assigned this to myself ( I hope that's

[jira] [Assigned] (KAFKA-13156) KafkaStatusBackingStore making incorrect assumption about order of task and connector delete events

[ https://issues.apache.org/jira/browse/KAFKA-13156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao reassigned KAFKA-13156: - Assignee: Sagar Rao (was: Chris Egerton) > KafkaStatusBackingStore making incorrect

[jira] [Updated] (KAFKA-14956) Flaky test org.apache.kafka.connect.integration.OffsetsApiIntegrationTest#testGetSinkConnectorOffsetsDifferentKafkaClusterTargeted

[ https://issues.apache.org/jira/browse/KAFKA-14956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao updated KAFKA-14956: -- Labels: flaky-test (was: ) > Flaky test >

[jira] [Updated] (KAFKA-14956) Flaky test org.apache.kafka.connect.integration.OffsetsApiIntegrationTest#testGetSinkConnectorOffsetsDifferentKafkaClusterTargeted

[ https://issues.apache.org/jira/browse/KAFKA-14956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao updated KAFKA-14956: -- Component/s: KafkaConnect > Flaky test >

[jira] [Updated] (KAFKA-14971) Flaky Test org.apache.kafka.connect.mirror.integration.IdentityReplicationIntegrationTest#testSyncTopicConfigs

[ https://issues.apache.org/jira/browse/KAFKA-14971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao updated KAFKA-14971: -- Labels: flaky-test mirror-maker (was: ) > Flaky Test >

[jira] [Created] (KAFKA-14997) JmxToolTest failing with initializationError

Sagar Rao created KAFKA-14997: - Summary: JmxToolTest failing with initializationError Key: KAFKA-14997 URL: https://issues.apache.org/jira/browse/KAFKA-14997 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-14971) Flaky Test org.apache.kafka.connect.mirror.integration.IdentityReplicationIntegrationTest#testSyncTopicConfigs

[ https://issues.apache.org/jira/browse/KAFKA-14971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao updated KAFKA-14971: -- Description: The test testSyncTopicConfigs in

[jira] [Created] (KAFKA-14971) Flaky Test org.apache.kafka.connect.mirror.integration.IdentityReplicationIntegrationTest#testSyncTopicConfigs

Sagar Rao created KAFKA-14971: - Summary: Flaky Test org.apache.kafka.connect.mirror.integration.IdentityReplicationIntegrationTest#testSyncTopicConfigs Key: KAFKA-14971 URL:

  1   2   3   4   5   >