[jira] [Commented] (KAFKA-13459) MM2 should be able to add the source offset to the record header

[ https://issues.apache.org/jira/browse/KAFKA-13459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17839717#comment-17839717 ] Viktor Somogyi-Vass commented on KAFKA-13459: - [~durban] have you planned to move ahead with

[jira] [Updated] (KAFKA-16596) Flaky test – org.apache.kafka.clients.ClientUtilsTest.testParseAndValidateAddressesWithReverseLookup()

[ https://issues.apache.org/jira/browse/KAFKA-16596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-16596: Fix Version/s: 3.6.3 > Flaky test – >

[jira] [Commented] (KAFKA-16596) Flaky test – org.apache.kafka.clients.ClientUtilsTest.testParseAndValidateAddressesWithReverseLookup()

[ https://issues.apache.org/jira/browse/KAFKA-16596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17839636#comment-17839636 ] Viktor Somogyi-Vass commented on KAFKA-16596: - Cherry-picked this onto 3.7 and 3.6 too. >

[jira] [Updated] (KAFKA-16596) Flaky test – org.apache.kafka.clients.ClientUtilsTest.testParseAndValidateAddressesWithReverseLookup()

[ https://issues.apache.org/jira/browse/KAFKA-16596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-16596: Fix Version/s: 3.7.1 > Flaky test – >

[jira] [Resolved] (KAFKA-16596) Flaky test – org.apache.kafka.clients.ClientUtilsTest.testParseAndValidateAddressesWithReverseLookup()

[ https://issues.apache.org/jira/browse/KAFKA-16596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass resolved KAFKA-16596. - Fix Version/s: 3.8.0 Assignee: Andras Katona Resolution: Fixed

[jira] [Commented] (KAFKA-16596) Flaky test – org.apache.kafka.clients.ClientUtilsTest.testParseAndValidateAddressesWithReverseLookup()

[ https://issues.apache.org/jira/browse/KAFKA-16596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17839624#comment-17839624 ] Viktor Somogyi-Vass commented on KAFKA-16596: - [~soarez] just merged the PR a couple of

[jira] [Comment Edited] (KAFKA-15649) Handle directory failure timeout

[ https://issues.apache.org/jira/browse/KAFKA-15649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836080#comment-17836080 ] Viktor Somogyi-Vass edited comment on KAFKA-15649 at 4/11/24 9:37 AM:

[jira] [Assigned] (KAFKA-15649) Handle directory failure timeout

[ https://issues.apache.org/jira/browse/KAFKA-15649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass reassigned KAFKA-15649: --- Assignee: Viktor Somogyi-Vass > Handle directory failure timeout >

[jira] [Commented] (KAFKA-15649) Handle directory failure timeout

[ https://issues.apache.org/jira/browse/KAFKA-15649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17824815#comment-17824815 ] Viktor Somogyi-Vass commented on KAFKA-15649: - [~soarez] would you mind if I picked this up?

[jira] [Commented] (KAFKA-13949) Connect /connectors endpoint should support querying the active topics and the task configs

[ https://issues.apache.org/jira/browse/KAFKA-13949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17814311#comment-17814311 ] Viktor Somogyi-Vass commented on KAFKA-13949: - [~wasniksudesh] feel free to ping me when

[jira] [Commented] (KAFKA-15366) Log directory failure integration test

[ https://issues.apache.org/jira/browse/KAFKA-15366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796284#comment-17796284 ] Viktor Somogyi-Vass commented on KAFKA-15366: - [~soarez] I think I'll separate testing the

[jira] [Updated] (KAFKA-15992) Make MM2 heartbeats topic name configurable

[ https://issues.apache.org/jira/browse/KAFKA-15992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-15992: Component/s: mirrormaker > Make MM2 heartbeats topic name configurable >

[jira] [Created] (KAFKA-15992) Make MM2 heartbeats topic name configurable

Viktor Somogyi-Vass created KAFKA-15992: --- Summary: Make MM2 heartbeats topic name configurable Key: KAFKA-15992 URL: https://issues.apache.org/jira/browse/KAFKA-15992 Project: Kafka

[jira] [Updated] (KAFKA-13922) Unable to generate coverage reports for the whole project

[ https://issues.apache.org/jira/browse/KAFKA-13922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-13922: Labels: cloudera (was: ) > Unable to generate coverage reports for the whole

[jira] [Comment Edited] (KAFKA-15366) Log directory failure integration test

[ https://issues.apache.org/jira/browse/KAFKA-15366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17793324#comment-17793324 ] Viktor Somogyi-Vass edited comment on KAFKA-15366 at 12/5/23 3:20 PM:

[jira] [Commented] (KAFKA-15366) Log directory failure integration test

[ https://issues.apache.org/jira/browse/KAFKA-15366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17793324#comment-17793324 ] Viktor Somogyi-Vass commented on KAFKA-15366: - [~soarez] did you have anything in mind other

[jira] [Commented] (KAFKA-14127) KIP-858: Handle JBOD broker disk failure in KRaft

[ https://issues.apache.org/jira/browse/KAFKA-14127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17793321#comment-17793321 ] Viktor Somogyi-Vass commented on KAFKA-14127: - I'll try one of the tests and perhaps review

[jira] [Assigned] (KAFKA-15366) Log directory failure integration test

[ https://issues.apache.org/jira/browse/KAFKA-15366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass reassigned KAFKA-15366: --- Assignee: Viktor Somogyi-Vass > Log directory failure integration test >

[jira] [Comment Edited] (KAFKA-14127) KIP-858: Handle JBOD broker disk failure in KRaft

[ https://issues.apache.org/jira/browse/KAFKA-14127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792858#comment-17792858 ] Viktor Somogyi-Vass edited comment on KAFKA-14127 at 12/4/23 1:50 PM:

[jira] [Commented] (KAFKA-14127) KIP-858: Handle JBOD broker disk failure in KRaft

[ https://issues.apache.org/jira/browse/KAFKA-14127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792858#comment-17792858 ] Viktor Somogyi-Vass commented on KAFKA-14127: - [~soarez] is there anything that I can pick

[jira] [Updated] (KAFKA-8128) Dynamic JAAS change for clients

[ https://issues.apache.org/jira/browse/KAFKA-8128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-8128: --- Labels: admin clients consumer need-kip producer (was: ) > Dynamic JAAS change for

[jira] [Commented] (KAFKA-8128) Dynamic JAAS change for clients

[ https://issues.apache.org/jira/browse/KAFKA-8128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791679#comment-17791679 ] Viktor Somogyi-Vass commented on KAFKA-8128: Have a KIP ready but will also do a PoC

[jira] [Commented] (KAFKA-15362) Resolve offline replicas in metadata cache

[ https://issues.apache.org/jira/browse/KAFKA-15362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790152#comment-17790152 ] Viktor Somogyi-Vass commented on KAFKA-15362: - [~soarez] do you think this ticket can be

[jira] [Updated] (KAFKA-8820) kafka-reassign-partitions.sh should support the KIP-455 API

[ https://issues.apache.org/jira/browse/KAFKA-8820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-8820: --- Fix Version/s: 2.6.0 (was: 2.5.0) >

[jira] [Commented] (KAFKA-8820) kafka-reassign-partitions.sh should support the KIP-455 API

[ https://issues.apache.org/jira/browse/KAFKA-8820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776151#comment-17776151 ] Viktor Somogyi-Vass commented on KAFKA-8820: Seems like the fix version is incorrect, it

[jira] [Commented] (KAFKA-9569) RemoteStorageManager implementation for HDFS storage.

[ https://issues.apache.org/jira/browse/KAFKA-9569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17766427#comment-17766427 ] Viktor Somogyi-Vass commented on KAFKA-9569: [~Ying Zheng], [~satish.duggana] is this plugin

[jira] [Commented] (KAFKA-15219) Support delegation tokens in KRaft

[ https://issues.apache.org/jira/browse/KAFKA-15219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17757246#comment-17757246 ] Viktor Somogyi-Vass commented on KAFKA-15219: - [~pprovenzano] thanks a lot for your work!

[jira] [Commented] (KAFKA-8128) Dynamic JAAS change for clients

[ https://issues.apache.org/jira/browse/KAFKA-8128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755108#comment-17755108 ] Viktor Somogyi-Vass commented on KAFKA-8128: I think for clients (since there is no REST API

[jira] [Updated] (KAFKA-8128) Dynamic JAAS change for clients

[ https://issues.apache.org/jira/browse/KAFKA-8128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-8128: --- Description: Clients using JAAS based authentication are now forced to restart

[jira] [Updated] (KAFKA-8128) Dynamic JAAS change for clients

[ https://issues.apache.org/jira/browse/KAFKA-8128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-8128: --- Summary: Dynamic JAAS change for clients (was: Dynamic delegation token change

[jira] [Commented] (KAFKA-15219) Support delegation tokens in KRaft

[ https://issues.apache.org/jira/browse/KAFKA-15219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17747550#comment-17747550 ] Viktor Somogyi-Vass commented on KAFKA-15219: - No problem, thanks for letting me know it in

[jira] [Updated] (KAFKA-15219) Support delegation tokens in KRaft

[ https://issues.apache.org/jira/browse/KAFKA-15219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-15219: Description: Delegation tokens have been created in KIP-48 and improved in

[jira] [Created] (KAFKA-15219) Support delegation tokens in KRaft

Viktor Somogyi-Vass created KAFKA-15219: --- Summary: Support delegation tokens in KRaft Key: KAFKA-15219 URL: https://issues.apache.org/jira/browse/KAFKA-15219 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-8128) Dynamic delegation token change possibility for consumer/producer

[ https://issues.apache.org/jira/browse/KAFKA-8128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17744640#comment-17744640 ] Viktor Somogyi-Vass commented on KAFKA-8128: So after 4 years (yes) I think I'll pick this

[jira] [Assigned] (KAFKA-8128) Dynamic delegation token change possibility for consumer/producer

[ https://issues.apache.org/jira/browse/KAFKA-8128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass reassigned KAFKA-8128: -- Assignee: Viktor Somogyi-Vass > Dynamic delegation token change possibility

[jira] [Updated] (KAFKA-15161) InvalidReplicationFactorException at connect startup

[ https://issues.apache.org/jira/browse/KAFKA-15161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-15161: Description: h2. Problem description In our system test environment in certain

[jira] [Updated] (KAFKA-15161) InvalidReplicationFactorException at connect startup

[ https://issues.apache.org/jira/browse/KAFKA-15161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-15161: Description: h2. Problem description In our system test environment in certain

[jira] [Updated] (KAFKA-15161) InvalidReplicationFactorException at connect startup

[ https://issues.apache.org/jira/browse/KAFKA-15161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-15161: Description: h2. Problem description In our system test environment in certain

[jira] [Updated] (KAFKA-15161) InvalidReplicationFactorException at connect startup

[ https://issues.apache.org/jira/browse/KAFKA-15161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-15161: Description: h2. Problem description In our system test environment in certain

[jira] [Updated] (KAFKA-15161) InvalidReplicationFactorException at connect startup

[ https://issues.apache.org/jira/browse/KAFKA-15161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-15161: Description: h2. Problem description In our system test environment in certain

[jira] [Updated] (KAFKA-15161) InvalidReplicationFactorException at connect startup

[ https://issues.apache.org/jira/browse/KAFKA-15161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-15161: Description: h2. Problem description In our system test environment in certain

[jira] [Updated] (KAFKA-15161) InvalidReplicationFactorException at connect startup

[ https://issues.apache.org/jira/browse/KAFKA-15161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-15161: Attachment: empty_metadata.patch > InvalidReplicationFactorException at connect

[jira] [Updated] (KAFKA-15161) InvalidReplicationFactorException at connect startup

[ https://issues.apache.org/jira/browse/KAFKA-15161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-15161: Issue Type: Bug (was: Improvement) > InvalidReplicationFactorException at

[jira] [Updated] (KAFKA-15161) InvalidReplicationFactorException at connect startup

[ https://issues.apache.org/jira/browse/KAFKA-15161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-15161: Description: h2. Problem description In our system test environment in certain

[jira] [Assigned] (KAFKA-15161) InvalidReplicationFactorException at connect startup

[ https://issues.apache.org/jira/browse/KAFKA-15161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass reassigned KAFKA-15161: --- Assignee: Viktor Somogyi-Vass > InvalidReplicationFactorException at

[jira] [Created] (KAFKA-15161) InvalidReplicationFactorException at connect startup

Viktor Somogyi-Vass created KAFKA-15161: --- Summary: InvalidReplicationFactorException at connect startup Key: KAFKA-15161 URL: https://issues.apache.org/jira/browse/KAFKA-15161 Project: Kafka

[jira] [Commented] (KAFKA-14112) Expose replication-offset-lag Mirror metric

[ https://issues.apache.org/jira/browse/KAFKA-14112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17735719#comment-17735719 ] Viktor Somogyi-Vass commented on KAFKA-14112: - Also I think we would need a small KIP for

[jira] [Commented] (KAFKA-14112) Expose replication-offset-lag Mirror metric

[ https://issues.apache.org/jira/browse/KAFKA-14112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17735718#comment-17735718 ] Viktor Somogyi-Vass commented on KAFKA-14112: - Yea, it's LEO-LRO. btw it's not contributed

[jira] [Resolved] (KAFKA-15059) Exactly-once source tasks fail to start during pending rebalances

[ https://issues.apache.org/jira/browse/KAFKA-15059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass resolved KAFKA-15059. - Resolution: Fixed [~ChrisEgerton] since the PR is merged, I resolve this

[jira] [Resolved] (KAFKA-12384) Flaky Test ListOffsetsRequestTest.testResponseIncludesLeaderEpoch

[ https://issues.apache.org/jira/browse/KAFKA-12384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass resolved KAFKA-12384. - Fix Version/s: 3.6.0 Resolution: Fixed > Flaky Test

[jira] [Commented] (KAFKA-12384) Flaky Test ListOffsetsRequestTest.testResponseIncludesLeaderEpoch

[ https://issues.apache.org/jira/browse/KAFKA-12384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17725761#comment-17725761 ] Viktor Somogyi-Vass commented on KAFKA-12384: - Ok, [~dajac] got to it sooner, resolving

[jira] [Updated] (KAFKA-13504) Retry connect internal topics' creation in case of InvalidReplicationFactorException

[ https://issues.apache.org/jira/browse/KAFKA-13504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-13504: Description: In case the Kafka Broker cluster and the Kafka Connect cluster is

[jira] [Commented] (KAFKA-12384) Flaky Test ListOffsetsRequestTest.testResponseIncludesLeaderEpoch

[ https://issues.apache.org/jira/browse/KAFKA-12384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17725703#comment-17725703 ] Viktor Somogyi-Vass commented on KAFKA-12384: - [~satish.duggana] I checked out recent

[jira] [Commented] (KAFKA-12384) Flaky Test ListOffsetsRequestTest.testResponseIncludesLeaderEpoch

[ https://issues.apache.org/jira/browse/KAFKA-12384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17725672#comment-17725672 ] Viktor Somogyi-Vass commented on KAFKA-12384: - Found another one in

[jira] [Assigned] (KAFKA-13337) Scanning for Connect plugins can fail with AccessDeniedException

[ https://issues.apache.org/jira/browse/KAFKA-13337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass reassigned KAFKA-13337: --- Assignee: Andras Katona (was: Tamás Héri) > Scanning for Connect plugins

[jira] [Commented] (KAFKA-13337) Scanning for Connect plugins can fail with AccessDeniedException

[ https://issues.apache.org/jira/browse/KAFKA-13337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17724260#comment-17724260 ] Viktor Somogyi-Vass commented on KAFKA-13337: - [~akatona] took this task over in a new PR:

[jira] [Updated] (KAFKA-14978) ExactlyOnceWorkerSourceTask does not remove parent metrics

[ https://issues.apache.org/jira/browse/KAFKA-14978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-14978: Fix Version/s: 3.5.0 3.3.3 > ExactlyOnceWorkerSourceTask does

[jira] [Resolved] (KAFKA-14929) Flaky KafkaStatusBackingStoreFormatTest#putTopicStateRetriableFailure

[ https://issues.apache.org/jira/browse/KAFKA-14929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass resolved KAFKA-14929. - Resolution: Fixed > Flaky

[jira] [Assigned] (KAFKA-14929) Flaky KafkaStatusBackingStoreFormatTest#putTopicStateRetriableFailure

[ https://issues.apache.org/jira/browse/KAFKA-14929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass reassigned KAFKA-14929: --- Assignee: Viktor Somogyi-Vass > Flaky

[jira] [Commented] (KAFKA-14112) Expose replication-offset-lag Mirror metric

[ https://issues.apache.org/jira/browse/KAFKA-14112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17698824#comment-17698824 ] Viktor Somogyi-Vass commented on KAFKA-14112: - [~elkkhan] do you have a PR for this, are you

[jira] [Assigned] (KAFKA-14667) Delayed leader election operation gets stuck in purgatory

[ https://issues.apache.org/jira/browse/KAFKA-14667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass reassigned KAFKA-14667: --- Assignee: Viktor Somogyi-Vass > Delayed leader election operation gets

[jira] [Updated] (KAFKA-14281) Multi-level rack awareness

[ https://issues.apache.org/jira/browse/KAFKA-14281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-14281: Labels: cloudera (was: ) > Multi-level rack awareness >

[jira] [Updated] (KAFKA-14250) Exception during normal operation in MirrorSourceTask causes the task to fail instead of shutting down gracefully

[ https://issues.apache.org/jira/browse/KAFKA-14250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-14250: Labels: cloudera (was: ) > Exception during normal operation in MirrorSourceTask

[jira] [Commented] (KAFKA-14331) Upgrade to Scala 2.13.10

[ https://issues.apache.org/jira/browse/KAFKA-14331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17623677#comment-17623677 ] Viktor Somogyi-Vass commented on KAFKA-14331: - Thanks [~mimaison], I'll resolve this as a

[jira] [Resolved] (KAFKA-14331) Upgrade to Scala 2.13.10

[ https://issues.apache.org/jira/browse/KAFKA-14331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass resolved KAFKA-14331. - Resolution: Duplicate > Upgrade to Scala 2.13.10 > > >

[jira] [Created] (KAFKA-14331) Upgrade to Scala 2.13.10

Viktor Somogyi-Vass created KAFKA-14331: --- Summary: Upgrade to Scala 2.13.10 Key: KAFKA-14331 URL: https://issues.apache.org/jira/browse/KAFKA-14331 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-14281) Multi-level rack awareness

[ https://issues.apache.org/jira/browse/KAFKA-14281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17617017#comment-17617017 ] Viktor Somogyi-Vass commented on KAFKA-14281: - Thanks [~ottomata] for the linked evaluation,

[jira] [Created] (KAFKA-14281) Multi-level rack awareness

Viktor Somogyi-Vass created KAFKA-14281: --- Summary: Multi-level rack awareness Key: KAFKA-14281 URL: https://issues.apache.org/jira/browse/KAFKA-14281 Project: Kafka Issue Type:

[jira] [Updated] (KAFKA-14250) Exception during normal operation in MirrorSourceTask causes the task to fail instead of shutting down gracefully

[ https://issues.apache.org/jira/browse/KAFKA-14250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-14250: Attachment: mm2.log > Exception during normal operation in MirrorSourceTask

[jira] [Created] (KAFKA-14250) Exception during normal operation in MirrorSourceTask causes the task to fail instead of shutting down gracefully

Viktor Somogyi-Vass created KAFKA-14250: --- Summary: Exception during normal operation in MirrorSourceTask causes the task to fail instead of shutting down gracefully Key: KAFKA-14250 URL:

[jira] [Updated] (KAFKA-13917) Avoid calling lookupCoordinator() in tight loop

[ https://issues.apache.org/jira/browse/KAFKA-13917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-13917: Affects Version/s: 3.3.0 3.2.1 > Avoid calling

[jira] [Updated] (KAFKA-6945) Add support to allow users to acquire delegation tokens for other users

[ https://issues.apache.org/jira/browse/KAFKA-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-6945: --- Affects Version/s: 3.3.0 > Add support to allow users to acquire delegation tokens

[jira] [Reopened] (KAFKA-6945) Add support to allow users to acquire delegation tokens for other users

[ https://issues.apache.org/jira/browse/KAFKA-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass reopened KAFKA-6945: > Add support to allow users to acquire delegation tokens for other users >

[jira] [Created] (KAFKA-13949) Connect /connectors endpoint should support querying the active topics and the task configs

Viktor Somogyi-Vass created KAFKA-13949: --- Summary: Connect /connectors endpoint should support querying the active topics and the task configs Key: KAFKA-13949 URL:

[jira] [Updated] (KAFKA-13917) Avoid calling lookupCoordinator() in tight loop

[ https://issues.apache.org/jira/browse/KAFKA-13917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-13917: Description: Currently the heartbeat thread's lookupCoordinator() is called in a

[jira] [Created] (KAFKA-13917) Avoid calling lookupCoordinator() in tight loop

Viktor Somogyi-Vass created KAFKA-13917: --- Summary: Avoid calling lookupCoordinator() in tight loop Key: KAFKA-13917 URL: https://issues.apache.org/jira/browse/KAFKA-13917 Project: Kafka

[jira] [Comment Edited] (KAFKA-9118) LogDirFailureHandler shouldn't use Zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538335#comment-17538335 ] Viktor Somogyi-Vass edited comment on KAFKA-9118 at 5/17/22 5:06 PM: -

[jira] [Assigned] (KAFKA-9118) LogDirFailureHandler shouldn't use Zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass reassigned KAFKA-9118: -- Assignee: David Arthur (was: Viktor Somogyi-Vass) > LogDirFailureHandler

[jira] [Commented] (KAFKA-9118) LogDirFailureHandler shouldn't use Zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538335#comment-17538335 ] Viktor Somogyi-Vass commented on KAFKA-9118: [~cmccabe] thanks for the comment, reassigned it

[jira] [Commented] (KAFKA-13848) Clients remain connected after SASL re-authentication fails

[ https://issues.apache.org/jira/browse/KAFKA-13848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17533793#comment-17533793 ] Viktor Somogyi-Vass commented on KAFKA-13848: - [~acsaki] please write an email to the

[jira] [Updated] (KAFKA-10430) Hook support

[ https://issues.apache.org/jira/browse/KAFKA-10430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-10430: Labels: cloudera (was: ) > Hook support > > > Key:

[jira] [Updated] (KAFKA-10430) Hook support

[ https://issues.apache.org/jira/browse/KAFKA-10430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-10430: Priority: Critical (was: Major) > Hook support > > >

[jira] [Assigned] (KAFKA-8195) Unstable Producer After Send Failure in Transaction

[ https://issues.apache.org/jira/browse/KAFKA-8195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass reassigned KAFKA-8195: -- Assignee: (was: Viktor Somogyi-Vass) > Unstable Producer After Send

[jira] [Updated] (KAFKA-10650) Use Murmur3 hashing instead of MD5 in SkimpyOffsetMap

[ https://issues.apache.org/jira/browse/KAFKA-10650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-10650: Labels: cloudera (was: ) > Use Murmur3 hashing instead of MD5 in SkimpyOffsetMap

[jira] [Updated] (KAFKA-13504) Retry connect internal topics' creation in case of InvalidReplicationFactorException

[ https://issues.apache.org/jira/browse/KAFKA-13504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-13504: Labels: cloudera (was: ) > Retry connect internal topics' creation in case of >

[jira] [Updated] (KAFKA-10586) Full support for distributed mode in dedicated MirrorMaker 2.0 clusters

[ https://issues.apache.org/jira/browse/KAFKA-10586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-10586: Labels: cloudera (was: ) > Full support for distributed mode in dedicated

[jira] [Updated] (KAFKA-6187) Remove the Logging class in favor of LazyLogging in scala-logging

[ https://issues.apache.org/jira/browse/KAFKA-6187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-6187: --- Priority: Minor (was: Major) > Remove the Logging class in favor of LazyLogging in

[jira] [Updated] (KAFKA-1774) REPL and Shell Client for Admin Message RQ/RP

[ https://issues.apache.org/jira/browse/KAFKA-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-1774: --- Priority: Minor (was: Major) > REPL and Shell Client for Admin Message RQ/RP >

[jira] [Updated] (KAFKA-8468) AdminClient.deleteTopics doesn't wait until topic is deleted

[ https://issues.apache.org/jira/browse/KAFKA-8468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-8468: --- Labels: cloudera (was: ) > AdminClient.deleteTopics doesn't wait until topic is

[jira] [Updated] (KAFKA-13240) HTTP TRACE should be disabled in Connect

[ https://issues.apache.org/jira/browse/KAFKA-13240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass updated KAFKA-13240: Labels: cloudera (was: ) > HTTP TRACE should be disabled in Connect >

[jira] [Resolved] (KAFKA-6084) ReassignPartitionsCommand should propagate JSON parsing failures

[ https://issues.apache.org/jira/browse/KAFKA-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass resolved KAFKA-6084. Fix Version/s: 2.8.0 Resolution: Fixed > ReassignPartitionsCommand should

[jira] [Resolved] (KAFKA-13442) REST API endpoint for fetching a connector's config definition

[ https://issues.apache.org/jira/browse/KAFKA-13442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass resolved KAFKA-13442. - Resolution: Duplicate > REST API endpoint for fetching a connector's config

[jira] [Assigned] (KAFKA-13504) Retry connect internal topics' creation in case of InvalidReplicationFactorException

[ https://issues.apache.org/jira/browse/KAFKA-13504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass reassigned KAFKA-13504: --- Assignee: Viktor Somogyi-Vass (was: Andras Katona) > Retry connect

[jira] [Resolved] (KAFKA-13452) MM2 creates invalid checkpoint when offset mapping is not available

[ https://issues.apache.org/jira/browse/KAFKA-13452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass resolved KAFKA-13452. - Resolution: Duplicate > MM2 creates invalid checkpoint when offset mapping is

[jira] [Assigned] (KAFKA-10586) Full support for distributed mode in dedicated MirrorMaker 2.0 clusters

[ https://issues.apache.org/jira/browse/KAFKA-10586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass reassigned KAFKA-10586: --- Assignee: Viktor Somogyi-Vass (was: Daniel Urban) > Full support for

[jira] [Assigned] (KAFKA-13459) MM2 should be able to add the source offset to the record header

[ https://issues.apache.org/jira/browse/KAFKA-13459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass reassigned KAFKA-13459: --- Assignee: Viktor Somogyi-Vass > MM2 should be able to add the source

[jira] [Assigned] (KAFKA-13659) MM2 should read all offset syncs at start up and should not set consumer offset higher than the end offset

[ https://issues.apache.org/jira/browse/KAFKA-13659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass reassigned KAFKA-13659: --- Assignee: Kanalas Vidor > MM2 should read all offset syncs at start up and

[jira] [Assigned] (KAFKA-13452) MM2 creates invalid checkpoint when offset mapping is not available

[ https://issues.apache.org/jira/browse/KAFKA-13452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass reassigned KAFKA-13452: --- Assignee: Viktor Somogyi-Vass > MM2 creates invalid checkpoint when offset

[jira] [Created] (KAFKA-13442) REST API endpoint for fetching a connector's config definition

Viktor Somogyi-Vass created KAFKA-13442: --- Summary: REST API endpoint for fetching a connector's config definition Key: KAFKA-13442 URL: https://issues.apache.org/jira/browse/KAFKA-13442

[jira] [Commented] (KAFKA-6668) Broker crashes on restart ,got a CorruptRecordException: Record size is smaller than minimum record overhead(14)

[ https://issues.apache.org/jira/browse/KAFKA-6668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17427097#comment-17427097 ] Viktor Somogyi-Vass commented on KAFKA-6668: [~little brother ma], [~alchimie], [~borisvu]

  1   2   3   >