[GitHub] [kafka] wenzelcheng closed pull request #11360: Floating point number comparison problem

wenzelcheng closed pull request #11360: URL: https://github.com/apache/kafka/pull/11360 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: jira-unsub

[GitHub] [kafka] lbradstreet opened a new pull request #11376: KAFKA-13342: LeaderAndIsrRequest should not be sent for topic queued for deletion

lbradstreet opened a new pull request #11376: URL: https://github.com/apache/kafka/pull/11376 In some cases a broker may be lost during a topic deletion and before its replica has moved to OfflineReplica state. When the broker comes back up the controller will send it a LeaderAndIsrReq

[jira] [Commented] (KAFKA-13331) Slow reassignments in 2.8 because of large number of UpdateMetadataResponseReceived(UpdateMetadataResponseData(errorCode=0),) Events

[ https://issues.apache.org/jira/browse/KAFKA-13331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17423761#comment-17423761 ] GEORGE LI commented on KAFKA-13331: --- besides slowness of the reassignments, when the

[jira] [Commented] (KAFKA-13342) LISR sent for topic queued for deletion in controller

[ https://issues.apache.org/jira/browse/KAFKA-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17423756#comment-17423756 ] Lucas Bradstreet commented on KAFKA-13342: -- Under some scenarios I think this c

[jira] [Updated] (KAFKA-13342) LISR sent for topic queued for deletion in controller

[ https://issues.apache.org/jira/browse/KAFKA-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucas Bradstreet updated KAFKA-13342: - Priority: Minor (was: Major) > LISR sent for topic queued for deletion in controller >

[jira] [Created] (KAFKA-13342) LISR sent for topic queued for deletion in controller

Lucas Bradstreet created KAFKA-13342: Summary: LISR sent for topic queued for deletion in controller Key: KAFKA-13342 URL: https://issues.apache.org/jira/browse/KAFKA-13342 Project: Kafka

[jira] [Created] (KAFKA-13341) Quotas are not applied to requests with null clientId

David Mao created KAFKA-13341: - Summary: Quotas are not applied to requests with null clientId Key: KAFKA-13341 URL: https://issues.apache.org/jira/browse/KAFKA-13341 Project: Kafka Issue Type: B

[jira] [Updated] (KAFKA-13341) Quotas are not applied to requests with null clientId

[ https://issues.apache.org/jira/browse/KAFKA-13341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Mao updated KAFKA-13341: -- Priority: Major (was: Minor) > Quotas are not applied to requests with null clientId > --

[GitHub] [kafka] satishd commented on pull request #11058: KAFKA-12802 Added a file based cache for consumed remote log metadata for each partition to avoid consuming again incase of broker restarts.

satishd commented on pull request #11058: URL: https://github.com/apache/kafka/pull/11058#issuecomment-933099724 Thanks @junrao for the review comments. Addressed them with the latest commit and replies. Added a scenario to verify checkpointed offsets in the [test](https://github.c

[GitHub] [kafka] upsidedownsmile opened a new pull request #11375: KAFKA-10865: Log transformed record in WorkerSinkTask

upsidedownsmile opened a new pull request #11375: URL: https://github.com/apache/kafka/pull/11375 This PR adds a log message with the **topic**, **key** and **value** to the transformed record in **WorkerSinkTask** similar to was already being done in **WorkerSinkTask**. Also fixed

[GitHub] [kafka] wenzelcheng closed pull request #11360: Floating point number comparison problem

wenzelcheng closed pull request #11360: URL: https://github.com/apache/kafka/pull/11360 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: jira-unsub