[jira] [Assigned] (KAFKA-13349) Allow Iterator.remove on KeyValueIterator

2021-10-05 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartłomiej Stachura reassigned KAFKA-13349: --- Assignee: Bartłomiej Stachura > Allow Iterator.remove on KeyValueItera

[jira] [Created] (KAFKA-13323) The words are ambiguous

2021-09-25 Thread Jira
李壮壮 created KAFKA-13323: --- Summary: The words are ambiguous Key: KAFKA-13323 URL: https://issues.apache.org/jira/browse/KAFKA-13323 Project: Kafka Issue Type: Improvement Components: clients

[jira] [Updated] (KAFKA-13323) The words are ambiguous

2021-09-25 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 李壮壮 updated KAFKA-13323: Description: In 'Fetcher' class, there is a field means consumer client should record whether the cached

[jira] [Comment Edited] (KAFKA-12764) Expand Gradle build for Scala 3.0 ?

2021-10-24 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-12764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17433454#comment-17433454 ] Dejan Stojadinović edited comment on KAFKA-12764 at 10/24/21, 4:14 PM

[jira] [Commented] (KAFKA-12764) Expand Gradle build for Scala 3.0 ?

2021-10-24 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-12764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17433452#comment-17433452 ] Dejan Stojadinović commented on KAFKA-12764: {color:blue}*+Related links/resources+:*{color

[jira] [Commented] (KAFKA-12764) Expand Gradle build for Scala 3.0 ?

2021-10-24 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-12764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17433454#comment-17433454 ] Dejan Stojadinović commented on KAFKA-12764: [~ijuma] Is it safe to say that Scala 3

[jira] [Comment Edited] (KAFKA-13289) Bulk processing correctly ordered input data through a join with kafka-streams results in `Skipping record for expired segment`

2021-12-23 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464313#comment-17464313 ] Eugen Dück edited comment on KAFKA-13289 at 12/24/21, 3:16 AM

[jira] [Commented] (KAFKA-13289) Bulk processing correctly ordered input data through a join with kafka-streams results in `Skipping record for expired segment`

2022-01-04 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468912#comment-17468912 ] Eugen Dück commented on KAFKA-13289: [~mjsax]  I tried setting `max.task.idle.ms` like so: {color

[jira] [Commented] (KAFKA-13289) Bulk processing correctly ordered input data through a join with kafka-streams results in `Skipping record for expired segment`

2022-01-04 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468913#comment-17468913 ] Eugen Dück commented on KAFKA-13289: [~mjsax]  I just retried with confluentinc/cp-kafka:7.0.1, i.e

[jira] [Comment Edited] (KAFKA-13289) Bulk processing correctly ordered input data through a join with kafka-streams results in `Skipping record for expired segment`

2022-01-04 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468913#comment-17468913 ] Eugen Dück edited comment on KAFKA-13289 at 1/5/22, 2:38 AM: - [~mjsax]  I

[jira] [Comment Edited] (KAFKA-13289) Bulk processing correctly ordered input data through a join with kafka-streams results in `Skipping record for expired segment`

2022-01-04 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468912#comment-17468912 ] Eugen Dück edited comment on KAFKA-13289 at 1/4/22, 11:34 PM: -- [~mjsax]  I

[jira] [Commented] (KAFKA-13289) Bulk processing correctly ordered input data through a join with kafka-streams results in `Skipping record for expired segment`

2022-01-04 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17469016#comment-17469016 ] Eugen Dück commented on KAFKA-13289: Yes, if you use Matthew's repo, which gives the "Ski

[jira] [Comment Edited] (KAFKA-13289) Bulk processing correctly ordered input data through a join with kafka-streams results in `Skipping record for expired segment`

2022-01-04 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17469016#comment-17469016 ] Eugen Dück edited comment on KAFKA-13289 at 1/5/22, 4:53 AM: - That would

[jira] [Comment Edited] (KAFKA-13289) Bulk processing correctly ordered input data through a join with kafka-streams results in `Skipping record for expired segment`

2021-12-22 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17447678#comment-17447678 ] Eugen Dück edited comment on KAFKA-13289 at 12/23/21, 2:01 AM: --- [~mjsax

[jira] [Commented] (KAFKA-13289) Bulk processing correctly ordered input data through a join with kafka-streams results in `Skipping record for expired segment`

2021-12-22 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464313#comment-17464313 ] Eugen Dück commented on KAFKA-13289: As the "Skipping record for expired segment" log

[jira] (KAFKA-13289) Bulk processing correctly ordered input data through a join with kafka-streams results in `Skipping record for expired segment`

2021-12-22 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13289 ] Eugen Dück deleted comment on KAFKA-13289: was (Author: eugendueck): As the "Skipping record for expired segment" log indicates the possibility of message loss, and we have now

[jira] [Commented] (KAFKA-13289) Bulk processing correctly ordered input data through a join with kafka-streams results in `Skipping record for expired segment`

2021-12-22 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464274#comment-17464274 ] Eugen Dück commented on KAFKA-13289: As the "Skipping record for expired segment" log

[jira] [Commented] (KAFKA-13289) Bulk processing correctly ordered input data through a join with kafka-streams results in `Skipping record for expired segment`

2021-11-22 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17447678#comment-17447678 ] Eugen Dück commented on KAFKA-13289: Matthias To quote from the issue: > left/outer join res

[jira] [Commented] (KAFKA-13289) Bulk processing correctly ordered input data through a join with kafka-streams results in `Skipping record for expired segment`

2021-11-22 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17447676#comment-17447676 ] Eugen Dück commented on KAFKA-13289: Thanks Matthew for your comments! Too bad Kafka Streams didn't

[jira] [Commented] (KAFKA-13289) Bulk processing correctly ordered input data through a join with kafka-streams results in `Skipping record for expired segment`

2021-11-21 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17447198#comment-17447198 ] Eugen Dück commented on KAFKA-13289: Matthias, Matthew If you have an opinion on whether you think

[jira] [Comment Edited] (KAFKA-13289) Bulk processing correctly ordered input data through a join with kafka-streams results in `Skipping record for expired segment`

2021-11-23 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17447676#comment-17447676 ] Eugen Dück edited comment on KAFKA-13289 at 11/24/21, 12:49 AM: Thanks

[jira] [Created] (KAFKA-13483) Stale Missing ISR on a partition after a zookeeper timeout

2021-11-25 Thread Jira
F Méthot created KAFKA-13483: Summary: Stale Missing ISR on a partition after a zookeeper timeout Key: KAFKA-13483 URL: https://issues.apache.org/jira/browse/KAFKA-13483 Project: Kafka Issue

[jira] [Updated] (KAFKA-13483) Stale Missing ISR on a partition after a zookeeper timeout

2021-11-25 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] F Méthot updated KAFKA-13483: - Description: We hit a situation where we had a Stale Missing ISR on a single partition on an output

[jira] [Updated] (KAFKA-13483) Stale Missing ISR on a partition after a zookeeper timeout

2021-11-25 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] F Méthot updated KAFKA-13483: - Description: We hit a situation where we had a Stale Missing ISR on a single partition on an output

[jira] [Updated] (KAFKA-13483) Stale Missing ISR on a partition after a zookeeper timeout

2021-11-25 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] F Méthot updated KAFKA-13483: - Description: We hit a situation where we had a Stale Missing ISR on a single partition on an output

[jira] [Commented] (KAFKA-6080) Transactional EoS for source connectors

2021-11-02 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-6080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437377#comment-17437377 ] Sönke Liebau commented on KAFKA-6080: - Are there any developments around this? I recently came across

[jira] [Commented] (KAFKA-6080) Transactional EoS for source connectors

2021-11-03 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-6080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437826#comment-17437826 ] Sönke Liebau commented on KAFKA-6080: - Thanks [~tombentley]!! I'll give that a read. > Transactio

[jira] [Commented] (KAFKA-6995) Make config "internal.leave.group.on.close" public

2021-12-01 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17451907#comment-17451907 ] Jørgen commented on KAFKA-6995: --- Are there any other ways to proactively leave the group when a KS stops

[jira] [Commented] (KAFKA-10503) MockProducer doesn't throw ClassCastException when no partition for topic

2021-12-09 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-10503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456308#comment-17456308 ] Gonzalo Muñoz Fernández commented on KAFKA-10503: - [~dhunziker] yes, if the serializers

[jira] [Commented] (KAFKA-13289) Bulk processing correctly ordered input data through a join with kafka-streams results in `Skipping record for expired segment`

2022-01-09 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17471729#comment-17471729 ] Eugen Dück commented on KAFKA-13289: After reading [https://lists.apache.org/thread

[jira] [Comment Edited] (KAFKA-13289) Bulk processing correctly ordered input data through a join with kafka-streams results in `Skipping record for expired segment`

2022-01-09 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17471729#comment-17471729 ] Eugen Dück edited comment on KAFKA-13289 at 1/10/22, 7:46 AM: -- After

[jira] [Commented] (KAFKA-13289) Bulk processing correctly ordered input data through a join with kafka-streams results in `Skipping record for expired segment`

2022-01-09 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17471710#comment-17471710 ] Eugen Dück commented on KAFKA-13289: Meanwhile I could reproduce the "Skipping record for ex

[jira] [Comment Edited] (KAFKA-13289) Bulk processing correctly ordered input data through a join with kafka-streams results in `Skipping record for expired segment`

2022-01-11 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17473235#comment-17473235 ] Eugen Dück edited comment on KAFKA-13289 at 1/12/22, 3:04 AM: -- {quote} bq

[jira] [Commented] (KAFKA-13289) Bulk processing correctly ordered input data through a join with kafka-streams results in `Skipping record for expired segment`

2022-01-11 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17473235#comment-17473235 ] Eugen Dück commented on KAFKA-13289: {quote} bq. The app uses a 0ms join window with a 0ms

[jira] [Commented] (KAFKA-13289) Bulk processing correctly ordered input data through a join with kafka-streams results in `Skipping record for expired segment`

2022-01-10 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472424#comment-17472424 ] Eugen Dück commented on KAFKA-13289: I (accidentally) noticed that one way to reproduce "Ski

[jira] [Updated] (KAFKA-13677) version 3.0.0 Processor implementation uses parameter record (restricted identifier)

2022-02-21 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aljoša Vrbanac updated KAFKA-13677: --- Affects Version/s: 2.7.0 > version 3.0.0 Processor implementation uses parameter rec

[jira] [Created] (KAFKA-13677) version 3.0.0 Processor implementation uses parameter record (restricted identifier)

2022-02-21 Thread Jira
Aljoša Vrbanac created KAFKA-13677: -- Summary: version 3.0.0 Processor implementation uses parameter record (restricted identifier) Key: KAFKA-13677 URL: https://issues.apache.org/jira/browse/KAFKA-13677

[jira] [Commented] (KAFKA-13626) NullPointerException in Selector.pollSelectionKeys: channel is null

2022-03-22 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17510377#comment-17510377 ] Daniel Häuser commented on KAFKA-13626: --- Happened again today. This time I had access

[jira] [Commented] (KAFKA-13626) NullPointerException in Selector.pollSelectionKeys: channel is null

2022-02-04 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17486916#comment-17486916 ] Daniel Häuser commented on KAFKA-13626: --- [~Kvicii]  I don't know exactly what happened

[jira] [Created] (KAFKA-13626) NullPointerException in Selector.pollSelectionKeys: channel is null

2022-01-28 Thread Jira
Daniel Häuser created KAFKA-13626: - Summary: NullPointerException in Selector.pollSelectionKeys: channel is null Key: KAFKA-13626 URL: https://issues.apache.org/jira/browse/KAFKA-13626 Project: Kafka

[jira] [Commented] (KAFKA-3790) Default options when removing ACLs do not comply with documentation

2022-02-09 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-3790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17489798#comment-17489798 ] Sébastien Launay commented on KAFKA-3790: - It's an oldie and since then we have access

[jira] [Resolved] (KAFKA-3790) Default options when removing ACLs do not comply with documentation

2022-02-09 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-3790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sébastien Launay resolved KAFKA-3790. - Resolution: Won't Fix > Default options when removing ACLs do not com

[jira] [Commented] (KAFKA-13289) Bulk processing correctly ordered input data through a join with kafka-streams results in `Skipping record for expired segment`

2022-02-06 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17487820#comment-17487820 ] Eugen Dück commented on KAFKA-13289: [~mjsax] Our Streams app has now been running in production

[jira] [Commented] (KAFKA-13596) ERROR Error while deleting segments for {topic} : java.nio.file.NoSuchFileException

2022-01-18 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478321#comment-17478321 ] 小小小杰 commented on KAFKA-13596: -- It appears by itself and no stable way of recurrence has been found

[jira] [Created] (KAFKA-13611) Failed reconfiguration of tasks can cause missing offset replications in MirrorCheckpointConnector

2022-01-21 Thread Jira
Aljoscha Pörtner created KAFKA-13611: Summary: Failed reconfiguration of tasks can cause missing offset replications in MirrorCheckpointConnector Key: KAFKA-13611 URL: https://issues.apache.org/jira/browse

[jira] [Updated] (KAFKA-13611) Failed reconfiguration of tasks can cause missing offset replications in MirrorCheckpointConnector

2022-01-21 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aljoscha Pörtner updated KAFKA-13611: - Description: Because the _knownConsumerGroups_ are stored within a variable

[jira] [Created] (KAFKA-13801) Kafka server does not respect MetricsReporter interface contract for dynamically configured reporters

2022-04-05 Thread Jira
Xavier Léauté created KAFKA-13801: - Summary: Kafka server does not respect MetricsReporter interface contract for dynamically configured reporters Key: KAFKA-13801 URL: https://issues.apache.org/jira/browse/KAFKA

[jira] [Commented] (KAFKA-6204) Interceptor and MetricsReporter should implement java.io.Closeable

2022-04-05 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-6204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17517651#comment-17517651 ] Xavier Léauté commented on KAFKA-6204: -- this was mostly fixed by KIP-376 https://cwiki.apache.org

[jira] [Updated] (KAFKA-13801) Kafka server does not respect MetricsReporter interface contract for dynamically configured reporters

2022-04-05 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté updated KAFKA-13801: -- Component/s: metrics > Kafka server does not respect MetricsReporter interface contr

[jira] [Commented] (KAFKA-12774) kafka-streams 2.8: logging in uncaught-exceptionhandler doesn't go through log4j

2022-04-06 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-12774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17517866#comment-17517866 ] Jørgen commented on KAFKA-12774: [~cadonna] : Sounds good to me. We still have the issue, but I'm

[jira] [Created] (KAFKA-13802) Uncaught exception in scheduled task 'flush-log' (kafka.utils.KafkaScheduler)

2022-04-06 Thread Jira
Stéphane Loeuillet created KAFKA-13802: -- Summary: Uncaught exception in scheduled task 'flush-log' (kafka.utils.KafkaScheduler) Key: KAFKA-13802 URL: https://issues.apache.org/jira/browse/KAFKA-13802

[jira] [Resolved] (KAFKA-6204) Interceptor and MetricsReporter should implement java.io.Closeable

2022-04-05 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-6204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté resolved KAFKA-6204. -- Fix Version/s: 3.2.0 Assignee: Xavier Léauté Resolution: Fixed > Intercep

[jira] [Updated] (KAFKA-13802) Uncaught exception in scheduled task 'flush-log' (kafka.utils.KafkaScheduler)

2022-04-06 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stéphane Loeuillet updated KAFKA-13802: --- Environment: Ubuntu 20.04.3 Adoptium 17.0.2_8 Kafka 2.13_3.1.0 with message format

[jira] [Updated] (KAFKA-13802) Uncaught exception in scheduled task 'flush-log' (kafka.utils.KafkaScheduler)

2022-04-06 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stéphane Loeuillet updated KAFKA-13802: --- Environment: Ubuntu 20.04.3 Adoptium 17.0.2_8 Kafka 2.13_3.1.0 with message format

[jira] [Updated] (KAFKA-13802) Uncaught exception in scheduled task 'flush-log' (kafka.utils.KafkaScheduler)

2022-04-06 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stéphane Loeuillet updated KAFKA-13802: --- Environment: Ubuntu 20.04.3 Adoptium 17.0.2_8 Kafka 2.13_3.1.0 with message format

[jira] [Updated] (KAFKA-6204) Interceptor and MetricsReporter should implement java.io.Closeable

2022-04-07 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-6204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté updated KAFKA-6204: - Fix Version/s: 3.3.0 (was: 3.2.0) > Interceptor and MetricsRepor

[jira] [Updated] (KAFKA-13831) Kafka retention can use old value of retention.ms

2022-04-15 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maciej Bryński updated KAFKA-13831: --- Description: Hi, I think I have found a bug in Kafka retention. I'm using Confluent

[jira] [Updated] (KAFKA-13831) Kafka retention can use old value of retention.ms

2022-04-15 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maciej Bryński updated KAFKA-13831: --- Description: Hi, I think I have found a bug in Kafka retention. I'm using Confluent

[jira] [Created] (KAFKA-13831) Kafka retention can use old value of retention.ms

2022-04-15 Thread Jira
Maciej Bryński created KAFKA-13831: -- Summary: Kafka retention can use old value of retention.ms Key: KAFKA-13831 URL: https://issues.apache.org/jira/browse/KAFKA-13831 Project: Kafka Issue

[jira] [Updated] (KAFKA-15375) When running in KRaft mode, LogManager may creates CleanShutdown file by mistake

2023-08-30 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-15375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] José Armando García Sancio updated KAFKA-15375: --- Affects Version/s: 3.5.1 3.4.1

[jira] [Updated] (KAFKA-15375) When running in KRaft mode, LogManager may creates CleanShutdown file by mistake

2023-08-30 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-15375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] José Armando García Sancio updated KAFKA-15375: --- Fix Version/s: 3.3.3 3.6.0

[jira] [Updated] (KAFKA-14273) Kafka doesn't start with KRaft on Windows

2023-09-07 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-14273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] José Armando García Sancio updated KAFKA-14273: --- Affects Version/s: (was: 3.4.1

[jira] [Updated] (KAFKA-14273) Kafka doesn't start with KRaft on Windows

2023-09-07 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-14273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] José Armando García Sancio updated KAFKA-14273: --- Affects Version/s: 3.5.1 3.4.1 > Ka

[jira] [Resolved] (KAFKA-14273) Kafka doesn't start with KRaft on Windows

2023-09-07 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-14273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] José Armando García Sancio resolved KAFKA-14273. Resolution: Fixed > Kafka doesn't start with KRaft on Wind

[jira] [Commented] (KAFKA-14273) Kafka doesn't start with KRaft on Windows

2023-09-07 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-14273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17762843#comment-17762843 ] José Armando García Sancio commented on KAFKA-14273: [~satish.duggana] I think

[jira] [Assigned] (KAFKA-14273) Kafka doesn't start with KRaft on Windows

2023-09-07 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-14273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] José Armando García Sancio reassigned KAFKA-14273: -- Assignee: José Armando García Sancio > Kafka doesn't st

[jira] [Updated] (KAFKA-14273) Kafka doesn't start with KRaft on Windows

2023-09-07 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-14273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] José Armando García Sancio updated KAFKA-14273: --- Fix Version/s: 3.6.0 > Kafka doesn't start with KRaft on Wind

[jira] [Commented] (KAFKA-15375) When running in KRaft mode, LogManager may creates CleanShutdown file by mistake

2023-09-06 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-15375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17762466#comment-17762466 ] José Armando García Sancio commented on KAFKA-15375: [~satish.duggana] this is major

[jira] [Resolved] (KAFKA-15375) When running in KRaft mode, LogManager may creates CleanShutdown file by mistake

2023-09-06 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-15375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] José Armando García Sancio resolved KAFKA-15375. Resolution: Fixed > When running in KRaft mode, LogManager

[jira] [Updated] (KAFKA-15375) When running in KRaft mode, LogManager may creates CleanShutdown file by mistake

2023-09-06 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-15375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] José Armando García Sancio updated KAFKA-15375: --- Fix Version/s: 3.6.0 (was: 3.7.0) > W

[jira] [Created] (KAFKA-15446) Upgrading from 2.0 to 2.8, with replica out of sync exceeding 12 hours

2023-09-08 Thread Jira
许胜斌 created KAFKA-15446: --- Summary: Upgrading from 2.0 to 2.8, with replica out of sync exceeding 12 hours Key: KAFKA-15446 URL: https://issues.apache.org/jira/browse/KAFKA-15446 Project: Kafka Issue

[jira] [Commented] (KAFKA-15446) Upgrading from 2.0 to 2.8, with replica out of sync exceeding 12 hours

2023-09-08 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-15446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17762999#comment-17762999 ] 许胜斌 commented on KAFKA-15446: - now when I restarted node 0, the error is: [2023-09-08 17:04:55,812] ERROR

[jira] [Commented] (KAFKA-15446) Upgrading from 2.0 to 2.8, with replica out of sync exceeding 12 hours

2023-09-08 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-15446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17762997#comment-17762997 ] 许胜斌 commented on KAFKA-15446: - What should we do now? I have restarted Node1 and Node2, but the problem has

[jira] [Updated] (KAFKA-14241) Implement the snapshot cleanup policy

2023-10-16 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-14241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] José Armando García Sancio updated KAFKA-14241: --- Fix Version/s: (was: 3.7.0) > Implement the snapshot clea

[jira] [Created] (KAFKA-15509) KRaft Controller doesn't consider brokers that are shutting down during topic creating

2023-09-26 Thread Jira
José Armando García Sancio created KAFKA-15509: -- Summary: KRaft Controller doesn't consider brokers that are shutting down during topic creating Key: KAFKA-15509 URL: https://issues.apache.org/jira

[jira] [Resolved] (KAFKA-15345) KRaft leader should notify the listener only when it has read up to the leader's epoch

2023-08-17 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-15345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] José Armando García Sancio resolved KAFKA-15345. Resolution: Fixed > KRaft leader should notify the listener o

[jira] [Created] (KAFKA-15345) KRaft leader should notify the listener only when it has read up to the leader's epoch

2023-08-15 Thread Jira
José Armando García Sancio created KAFKA-15345: -- Summary: KRaft leader should notify the listener only when it has read up to the leader's epoch Key: KAFKA-15345 URL: https://issues.apache.org/jira

[jira] [Comment Edited] (KAFKA-7699) Improve wall-clock time punctuations

2023-08-22 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-7699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17757383#comment-17757383 ] François Rosière edited comment on KAFKA-7699 at 8/22/23 11:16 AM

[jira] [Commented] (KAFKA-7699) Improve wall-clock time punctuations

2023-08-22 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-7699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17757383#comment-17757383 ] François Rosière commented on KAFKA-7699: - Would be great to have such kind of support into Kafka

[jira] [Updated] (KAFKA-13913) Provide builders for KafkaProducer/KafkaConsumer and KafkaStreams

2022-05-18 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] François Rosière updated KAFKA-13913: - Fix Version/s: 3.3.0 > Provide builders for KafkaProducer/KafkaConsu

[jira] [Updated] (KAFKA-13913) Provide builders for KafkaProducer/KafkaConsumer and KafkaStreams

2022-05-18 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] François Rosière updated KAFKA-13913: - Description: To have more flexibility, builders should be provided for the following

[jira] [Updated] (KAFKA-13913) Provide builders for KafkaProducer/KafkaConsumer and KafkaStreams

2022-05-18 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] François Rosière updated KAFKA-13913: - Description: To have more flexibility, builders should be provided for the following

[jira] [Updated] (KAFKA-13913) Provide builders for KafkaProducer/KafkaConsumer and KafkaStreams

2022-05-18 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] François Rosière updated KAFKA-13913: - Description: To have more flexibility, builders should be provided for the following

[jira] [Updated] (KAFKA-13913) Provide builders for KafkaProducer/KafkaConsumer and KafkaStreams

2022-05-18 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] François Rosière updated KAFKA-13913: - Affects Version/s: 3.2.0 > Provide builders for KafkaProducer/KafkaConsu

[jira] [Created] (KAFKA-13913) Provide builders for KafkaProducer/KafkaConsumer and KafkaStreams

2022-05-18 Thread Jira
François Rosière created KAFKA-13913: Summary: Provide builders for KafkaProducer/KafkaConsumer and KafkaStreams Key: KAFKA-13913 URL: https://issues.apache.org/jira/browse/KAFKA-13913 Project

[jira] [Updated] (KAFKA-13864) Change the visibility of a KafkaProducer and KafkaConsumer constructor

2022-05-18 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] François Rosière updated KAFKA-13864: - Labels: (was: needs-kip) > Change the visibility of a KafkaProducer and KafkaConsu

[jira] [Resolved] (KAFKA-13864) Change the visibility of a KafkaProducer and KafkaConsumer constructor

2022-05-18 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] François Rosière resolved KAFKA-13864. -- Resolution: Won't Do > Change the visibility of a KafkaProducer and KafkaConsu

[jira] [Assigned] (KAFKA-13864) Change the visibility of a KafkaProducer and KafkaConsumer constructor

2022-05-18 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] François Rosière reassigned KAFKA-13864: Assignee: François Rosière (was: lqjacklee) > Change the visibil

[jira] [Commented] (KAFKA-13864) Change the visibility of a KafkaProducer and KafkaConsumer constructor

2022-05-18 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538617#comment-17538617 ] François Rosière commented on KAFKA-13864: -- This issue won't be implemented as KIP-832

[jira] [Commented] (KAFKA-13913) Provide builders for KafkaProducer/KafkaConsumer and KafkaStreams

2022-05-19 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17539801#comment-17539801 ] François Rosière commented on KAFKA-13913: -- [~mjsax] , thanks for your comment. The two

[jira] [Created] (KAFKA-14094) KIP-853: KRaft Voters Change

2022-07-21 Thread Jira
José Armando García Sancio created KAFKA-14094: -- Summary: KIP-853: KRaft Voters Change Key: KAFKA-14094 URL: https://issues.apache.org/jira/browse/KAFKA-14094 Project: Kafka

[jira] [Created] (KAFKA-14116) Update and add all of the Kafka Message Schemas

2022-07-27 Thread Jira
José Armando García Sancio created KAFKA-14116: -- Summary: Update and add all of the Kafka Message Schemas Key: KAFKA-14116 URL: https://issues.apache.org/jira/browse/KAFKA-14116 Project

[jira] [Created] (KAFKA-14113) KIP-856: KRaft Disk Failure Recovery

2022-07-27 Thread Jira
José Armando García Sancio created KAFKA-14113: -- Summary: KIP-856: KRaft Disk Failure Recovery Key: KAFKA-14113 URL: https://issues.apache.org/jira/browse/KAFKA-14113 Project: Kafka

[jira] [Created] (KAFKA-14118) Generate and persist storage uuiid

2022-07-27 Thread Jira
José Armando García Sancio created KAFKA-14118: -- Summary: Generate and persist storage uuiid Key: KAFKA-14118 URL: https://issues.apache.org/jira/browse/KAFKA-14118 Project: Kafka

[jira] [Commented] (KAFKA-13864) Change the visibility of a KafkaProducer and KafkaConsumer constructor

2022-05-02 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17530697#comment-17530697 ] François Rosière commented on KAFKA-13864: -- KIP looks overkill in this specific case as we

[jira] [Comment Edited] (KAFKA-13864) Change the visibility of a KafkaProducer and KafkaConsumer constructor

2022-05-02 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17530697#comment-17530697 ] François Rosière edited comment on KAFKA-13864 at 5/2/22 11:59 AM

[jira] [Updated] (KAFKA-13864) Change the visibility of a KafkaProducer and KafkaConsumer constructor

2022-05-02 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] François Rosière updated KAFKA-13864: - Description: To allow implementing Spring managed interceptors for producers

[jira] [Updated] (KAFKA-13864) Change the visibility of a KafkaProducer and KafkaConsumer constructor

2022-05-02 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] François Rosière updated KAFKA-13864: - Description: To allow implementing Spring managed interceptors for producers

[jira] [Updated] (KAFKA-13864) Change the visibility of a KafkaProducer and KafkaConsumer constructor

2022-05-02 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] François Rosière updated KAFKA-13864: - Description: To allow implementing Spring managed interceptors for producers

[jira] [Updated] (KAFKA-13864) Change the visibility of a KafkaProducer and KafkaConsumer constructor

2022-05-02 Thread Jira
[ https://issues.apache.org/jira/browse/KAFKA-13864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] François Rosière updated KAFKA-13864: - Description: To allow implementing Spring managed interceptors for producers

<    3   4   5   6   7   8   9   10   11   12   >