[jira] [Created] (KAFKA-15817) Avoid reconnecting to the same IP address if multiple addresses are available

2023-11-13 Thread Bob Barrett (Jira)
Bob Barrett created KAFKA-15817: --- Summary: Avoid reconnecting to the same IP address if multiple addresses are available Key: KAFKA-15817 URL: https://issues.apache.org/jira/browse/KAFKA-15817 Project:

[jira] [Assigned] (KAFKA-15817) Avoid reconnecting to the same IP address if multiple addresses are available

2023-11-13 Thread Bob Barrett (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-15817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett reassigned KAFKA-15817: --- Assignee: Bob Barrett > Avoid reconnecting to the same IP address if multiple addresses

[jira] [Created] (KAFKA-12193) Re-resolve IPs when a client is disconnected

2021-01-13 Thread Bob Barrett (Jira)
Bob Barrett created KAFKA-12193: --- Summary: Re-resolve IPs when a client is disconnected Key: KAFKA-12193 URL: https://issues.apache.org/jira/browse/KAFKA-12193 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-10860) JmxTool fails with NPE when object-name contains a wildcard

2020-12-16 Thread Bob Barrett (Jira)
Bob Barrett created KAFKA-10860: --- Summary: JmxTool fails with NPE when object-name contains a wildcard Key: KAFKA-10860 URL: https://issues.apache.org/jira/browse/KAFKA-10860 Project: Kafka

[jira] [Commented] (KAFKA-10635) Streams application fails with OutOfOrderSequenceException after rolling restarts of brokers

2020-11-03 Thread Bob Barrett (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-10635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17225752#comment-17225752 ] Bob Barrett commented on KAFKA-10635: - [~ascii80] would you be able to upload more client and broker

[jira] [Resolved] (KAFKA-10282) Log metrics are removed if a log is deleted and re-created quickly enough

2020-07-31 Thread Bob Barrett (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-10282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett resolved KAFKA-10282. - Resolution: Fixed > Log metrics are removed if a log is deleted and re-created quickly enough >

[jira] [Updated] (KAFKA-10320) Log metrics for future logs never have the is-future tag removed

2020-07-28 Thread Bob Barrett (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-10320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett updated KAFKA-10320: Priority: Minor (was: Major) > Log metrics for future logs never have the is-future tag removed

[jira] [Updated] (KAFKA-10320) Log metrics for future logs never have the is-future tag removed

2020-07-28 Thread Bob Barrett (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-10320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett updated KAFKA-10320: Description: When we create future logs as part of moving replicas between log dirs, the Log

[jira] [Created] (KAFKA-10320) Log metrics for future logs never have the is-future tag removed

2020-07-28 Thread Bob Barrett (Jira)
Bob Barrett created KAFKA-10320: --- Summary: Log metrics for future logs never have the is-future tag removed Key: KAFKA-10320 URL: https://issues.apache.org/jira/browse/KAFKA-10320 Project: Kafka

[jira] [Updated] (KAFKA-10197) Elect preferred leader when completing a partition reassignment

2020-06-24 Thread Bob Barrett (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett updated KAFKA-10197: Description: Currently, when completing a partition reassignment, we elect a leader from the new

[jira] [Created] (KAFKA-10197) Elect preferred leader when completing a partition reassignment

2020-06-24 Thread Bob Barrett (Jira)
Bob Barrett created KAFKA-10197: --- Summary: Elect preferred leader when completing a partition reassignment Key: KAFKA-10197 URL: https://issues.apache.org/jira/browse/KAFKA-10197 Project: Kafka

[jira] [Assigned] (KAFKA-10149) Do not prevent automatic preferred election when reassignment in progress

2020-06-11 Thread Bob Barrett (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-10149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett reassigned KAFKA-10149: --- Assignee: Bob Barrett > Do not prevent automatic preferred election when reassignment in

[jira] [Updated] (KAFKA-10059) KafkaAdminClient returns null OffsetAndMetadata value when there is no committed offset for a partition

2020-05-28 Thread Bob Barrett (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-10059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett updated KAFKA-10059: Description: When listing consumer group offsets through the admin client, the map that we

[jira] [Updated] (KAFKA-10059) KafkaAdminClient returns null OffsetAndMetadata value when there is no committed offset for a partition

2020-05-28 Thread Bob Barrett (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-10059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett updated KAFKA-10059: Description: When listing consumer group offsets through the admin client, the map that we

[jira] [Updated] (KAFKA-10059) KafkaAdminClient returns null OffsetAndMetadata value when there is no committed offset for a partition

2020-05-28 Thread Bob Barrett (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-10059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett updated KAFKA-10059: Description: When listing consumer group offsets through the admin client, the map that we

[jira] [Updated] (KAFKA-10059) KafkaAdminClient returns null OffsetAndMetadata value when there is no committed offset for a partition

2020-05-28 Thread Bob Barrett (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-10059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett updated KAFKA-10059: Description: When listing consumer group offsets through the admin client, the map that we

[jira] [Created] (KAFKA-10059) KafkaAdminClient returns null OffsetAndMetadata value when there is no committed offset for a partition

2020-05-28 Thread Bob Barrett (Jira)
Bob Barrett created KAFKA-10059: --- Summary: KafkaAdminClient returns null OffsetAndMetadata value when there is no committed offset for a partition Key: KAFKA-10059 URL:

[jira] [Created] (KAFKA-9811) TransactionMetadata state and pendingState are non-volatile and read outside the metadata lock

2020-04-02 Thread Bob Barrett (Jira)
Bob Barrett created KAFKA-9811: -- Summary: TransactionMetadata state and pendingState are non-volatile and read outside the metadata lock Key: KAFKA-9811 URL: https://issues.apache.org/jira/browse/KAFKA-9811

[jira] [Created] (KAFKA-9788) Sensor name collision for group and transaction coordinator load metrics

2020-03-30 Thread Bob Barrett (Jira)
Bob Barrett created KAFKA-9788: -- Summary: Sensor name collision for group and transaction coordinator load metrics Key: KAFKA-9788 URL: https://issues.apache.org/jira/browse/KAFKA-9788 Project: Kafka

[jira] [Updated] (KAFKA-9749) TransactionMarkerRequestCompletionHandler should treat storage exceptions as retriable

2020-03-23 Thread Bob Barrett (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-9749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett updated KAFKA-9749: --- Affects Version/s: 2.5.0 > TransactionMarkerRequestCompletionHandler should treat storage exceptions

[jira] [Created] (KAFKA-9750) Flaky test kafka.server.ReplicaManagerTest.testFencedErrorCausedByBecomeLeader

2020-03-23 Thread Bob Barrett (Jira)
Bob Barrett created KAFKA-9750: -- Summary: Flaky test kafka.server.ReplicaManagerTest.testFencedErrorCausedByBecomeLeader Key: KAFKA-9750 URL: https://issues.apache.org/jira/browse/KAFKA-9750 Project:

[jira] [Updated] (KAFKA-9749) TransactionMarkerRequestCompletionHandler should treat storage exceptions as retriable

2020-03-23 Thread Bob Barrett (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-9749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett updated KAFKA-9749: --- Component/s: core > TransactionMarkerRequestCompletionHandler should treat storage exceptions as >

[jira] [Assigned] (KAFKA-9749) TransactionMarkerRequestCompletionHandler should treat storage exceptions as retriable

2020-03-23 Thread Bob Barrett (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-9749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett reassigned KAFKA-9749: -- Assignee: Bob Barrett > TransactionMarkerRequestCompletionHandler should treat storage

[jira] [Created] (KAFKA-9749) TransactionMarkerRequestCompletionHandler should treat storage exceptions as retriable

2020-03-23 Thread Bob Barrett (Jira)
Bob Barrett created KAFKA-9749: -- Summary: TransactionMarkerRequestCompletionHandler should treat storage exceptions as retriable Key: KAFKA-9749 URL: https://issues.apache.org/jira/browse/KAFKA-9749

[jira] [Assigned] (KAFKA-9666) Transactional producer Epoch could not be reset

2020-03-05 Thread Bob Barrett (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-9666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett reassigned KAFKA-9666: -- Assignee: Bob Barrett > Transactional producer Epoch could not be reset >

[jira] [Created] (KAFKA-9276) Unclear warning due to empty throttled fetch response

2019-12-05 Thread Bob Barrett (Jira)
Bob Barrett created KAFKA-9276: -- Summary: Unclear warning due to empty throttled fetch response Key: KAFKA-9276 URL: https://issues.apache.org/jira/browse/KAFKA-9276 Project: Kafka Issue Type:

[jira] [Updated] (KAFKA-9105) Truncate producer state when incrementing log start offset

2019-10-25 Thread Bob Barrett (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-9105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett updated KAFKA-9105: --- Description: As part of the fix for KAFKA-7190, we removed the ProducerStateManager.truncateHead

[jira] [Created] (KAFKA-9105) Truncate producer state when incrementing log start offset

2019-10-25 Thread Bob Barrett (Jira)
Bob Barrett created KAFKA-9105: -- Summary: Truncate producer state when incrementing log start offset Key: KAFKA-9105 URL: https://issues.apache.org/jira/browse/KAFKA-9105 Project: Kafka Issue

[jira] [Created] (KAFKA-9038) Allow creating partitions while partition reassignment is in progress

2019-10-14 Thread Bob Barrett (Jira)
Bob Barrett created KAFKA-9038: -- Summary: Allow creating partitions while partition reassignment is in progress Key: KAFKA-9038 URL: https://issues.apache.org/jira/browse/KAFKA-9038 Project: Kafka

[jira] [Assigned] (KAFKA-8374) KafkaApis.handleLeaderAndIsrRequest not robust to ZooKeeper exceptions

2019-08-20 Thread Bob Barrett (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-8374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett reassigned KAFKA-8374: -- Assignee: Bob Barrett > KafkaApis.handleLeaderAndIsrRequest not robust to ZooKeeper

[jira] [Created] (KAFKA-8805) Bump producer epoch following recoverable errors

2019-08-14 Thread Bob Barrett (JIRA)
Bob Barrett created KAFKA-8805: -- Summary: Bump producer epoch following recoverable errors Key: KAFKA-8805 URL: https://issues.apache.org/jira/browse/KAFKA-8805 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-8325) Remove from the incomplete set failed. This should be impossible

2019-08-06 Thread Bob Barrett (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-8325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16901429#comment-16901429 ] Bob Barrett commented on KAFKA-8325: Looks like the problem is that when handling a MESSAGE_TOO_LARGE

[jira] [Commented] (KAFKA-8325) Remove from the incomplete set failed. This should be impossible

2019-07-25 Thread Bob Barrett (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-8325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16893166#comment-16893166 ] Bob Barrett commented on KAFKA-8325: [~mbarbon] Would you be able to upload producer logs from around

[jira] [Commented] (KAFKA-7190) Under low traffic conditions purging repartition topics cause WARN statements about UNKNOWN_PRODUCER_ID

2019-07-24 Thread Bob Barrett (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16892046#comment-16892046 ] Bob Barrett commented on KAFKA-7190: The periodic producer expiration check expires producers if 1)

[jira] [Created] (KAFKA-8710) InitProducerId changes for KIP-360

2019-07-24 Thread Bob Barrett (JIRA)
Bob Barrett created KAFKA-8710: -- Summary: InitProducerId changes for KIP-360 Key: KAFKA-8710 URL: https://issues.apache.org/jira/browse/KAFKA-8710 Project: Kafka Issue Type: Improvement

[jira] [Assigned] (KAFKA-8325) Remove from the incomplete set failed. This should be impossible

2019-07-23 Thread Bob Barrett (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-8325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett reassigned KAFKA-8325: -- Assignee: Bob Barrett > Remove from the incomplete set failed. This should be impossible >

[jira] [Assigned] (KAFKA-8635) Unnecessary wait when looking up coordinator before transactional request

2019-07-08 Thread Bob Barrett (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-8635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett reassigned KAFKA-8635: -- Assignee: Bob Barrett > Unnecessary wait when looking up coordinator before transactional

[jira] [Assigned] (KAFKA-8614) Rename the `responses` field of IncrementalAlterConfigsResponse to match AlterConfigs

2019-06-28 Thread Bob Barrett (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-8614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett reassigned KAFKA-8614: -- Assignee: Bob Barrett > Rename the `responses` field of IncrementalAlterConfigsResponse to

[jira] [Updated] (KAFKA-8614) Rename the `responses` field of IncrementalAlterConfigsResponse to match AlterConfigs

2019-06-28 Thread Bob Barrett (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-8614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett updated KAFKA-8614: --- Description: IncrementalAlterConfigsResponse and AlterConfigsResponse have an identical structure

[jira] [Updated] (KAFKA-8614) Rename the `responses` field of IncrementalAlterConfigsResponse to match AlterConfigs

2019-06-28 Thread Bob Barrett (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-8614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett updated KAFKA-8614: --- Description: IncrementalAlterConfigsResponse and AlterConfigsResponse have an identical structure

[jira] [Created] (KAFKA-8614) Rename the `responses` field of IncrementalAlterConfigsResponse to match AlterConfigs

2019-06-28 Thread Bob Barrett (JIRA)
Bob Barrett created KAFKA-8614: -- Summary: Rename the `responses` field of IncrementalAlterConfigsResponse to match AlterConfigs Key: KAFKA-8614 URL: https://issues.apache.org/jira/browse/KAFKA-8614

[jira] [Assigned] (KAFKA-8002) Replica reassignment to new log dir may not complete if future and current replicas segment files have different base offsets

2019-02-26 Thread Bob Barrett (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-8002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett reassigned KAFKA-8002: -- Assignee: Bob Barrett > Replica reassignment to new log dir may not complete if future and

[jira] [Commented] (KAFKA-6833) KafkaProducer throws "Invalid partition given with record" exception

2018-12-28 Thread Bob Barrett (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730421#comment-16730421 ] Bob Barrett commented on KAFKA-6833: Thanks for the suggestion, [~ChrisEgerton]! I agree with

[jira] [Created] (KAFKA-7607) NetworkClientUtils.sendAndReceive can take a long time to return during shutdown

2018-11-07 Thread Bob Barrett (JIRA)
Bob Barrett created KAFKA-7607: -- Summary: NetworkClientUtils.sendAndReceive can take a long time to return during shutdown Key: KAFKA-7607 URL: https://issues.apache.org/jira/browse/KAFKA-7607 Project:

[jira] [Updated] (KAFKA-7467) NoSuchElementException is raised because controlBatch is empty

2018-10-01 Thread Bob Barrett (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-7467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett updated KAFKA-7467: --- Description: Somehow, log cleaner died because of NoSuchElementException when it calls

[jira] [Assigned] (KAFKA-7467) NoSuchElementException is raised because controlBatch is empty

2018-10-01 Thread Bob Barrett (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-7467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett reassigned KAFKA-7467: -- Assignee: Bob Barrett > NoSuchElementException is raised because controlBatch is empty >

[jira] [Updated] (KAFKA-7467) NoSuchElementException is raised because controlBatch is empty

2018-10-01 Thread Bob Barrett (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-7467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett updated KAFKA-7467: --- Description: Somehow, log cleaner died because of NoSuchElementException when it calls

[jira] [Assigned] (KAFKA-7400) Compacted topic segments that precede the log start offset are not cleaned up

2018-09-13 Thread Bob Barrett (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-7400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett reassigned KAFKA-7400: -- Assignee: Bob Barrett > Compacted topic segments that precede the log start offset are not

[jira] [Updated] (KAFKA-7401) Broker fails to start when recovering a segment from before the log start offset

2018-09-11 Thread Bob Barrett (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-7401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett updated KAFKA-7401: --- Affects Version/s: (was: 2.0.0) > Broker fails to start when recovering a segment from before

[jira] [Updated] (KAFKA-7401) Broker fails to start when recovering a segment from before the log start offset

2018-09-11 Thread Bob Barrett (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-7401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett updated KAFKA-7401: --- Description: If a segment needs to be recovered (for example, because of a missing index file or

[jira] [Created] (KAFKA-7401) Broker fails to start when recovering a segment from before the log start offset

2018-09-11 Thread Bob Barrett (JIRA)
Bob Barrett created KAFKA-7401: -- Summary: Broker fails to start when recovering a segment from before the log start offset Key: KAFKA-7401 URL: https://issues.apache.org/jira/browse/KAFKA-7401 Project:

[jira] [Updated] (KAFKA-7400) Compacted topic segments that precede the log start offset are not cleaned up

2018-09-11 Thread Bob Barrett (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-7400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett updated KAFKA-7400: --- Priority: Minor (was: Major) > Compacted topic segments that precede the log start offset are not

[jira] [Created] (KAFKA-7400) Compacted topic segments that precede the log start offset are not cleaned up

2018-09-11 Thread Bob Barrett (JIRA)
Bob Barrett created KAFKA-7400: -- Summary: Compacted topic segments that precede the log start offset are not cleaned up Key: KAFKA-7400 URL: https://issues.apache.org/jira/browse/KAFKA-7400 Project:

[jira] [Assigned] (KAFKA-6833) KafkaProducer throws "Invalid partition given with record" exception

2018-08-14 Thread Bob Barrett (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett reassigned KAFKA-6833: -- Assignee: Bob Barrett > KafkaProducer throws "Invalid partition given with record" exception

[jira] [Assigned] (KAFKA-6639) Follower may have sparse index if catching up

2018-07-25 Thread Bob Barrett (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett reassigned KAFKA-6639: -- Assignee: Bob Barrett > Follower may have sparse index if catching up >

[jira] [Assigned] (KAFKA-7164) Follower should truncate after every leader epoch change

2018-07-17 Thread Bob Barrett (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-7164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett reassigned KAFKA-7164: -- Assignee: Bob Barrett > Follower should truncate after every leader epoch change >