[jira] [Resolved] (KAFKA-16350) StateUpdater does not init transaction after canceling task close action

[ https://issues.apache.org/jira/browse/KAFKA-16350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna resolved KAFKA-16350. --- Resolution: Fixed > StateUpdater does not init transaction after canceling task close

[jira] [Commented] (KAFKA-16350) StateUpdater does not init transaction after canceling task close action

[ https://issues.apache.org/jira/browse/KAFKA-16350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847008#comment-17847008 ] Bruno Cadonna commented on KAFKA-16350: --- This issue should be gone after the following PR:

[jira] [Assigned] (KAFKA-16774) fix flaky StreamThreadTest#shouldCloseAllTaskProducersOnCloseIfEosEnabled

[ https://issues.apache.org/jira/browse/KAFKA-16774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna reassigned KAFKA-16774: - Assignee: Bruno Cadonna > fix flaky

[jira] [Commented] (KAFKA-16774) fix flaky StreamThreadTest#shouldCloseAllTaskProducersOnCloseIfEosEnabled

[ https://issues.apache.org/jira/browse/KAFKA-16774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846959#comment-17846959 ] Bruno Cadonna commented on KAFKA-16774: --- Looking at the test, I think we can remove that test and

[jira] [Commented] (KAFKA-16774) fix flaky StreamThreadTest#shouldCloseAllTaskProducersOnCloseIfEosEnabled

[ https://issues.apache.org/jira/browse/KAFKA-16774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846940#comment-17846940 ] Bruno Cadonna commented on KAFKA-16774: --- [~chia7712] Thank you for your analysis! Without looking

[jira] [Updated] (KAFKA-14567) Kafka Streams crashes after ProducerFencedException

[ https://issues.apache.org/jira/browse/KAFKA-14567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna updated KAFKA-14567: -- Fix Version/s: 3.8.0 > Kafka Streams crashes after ProducerFencedException >

[jira] [Updated] (KAFKA-14567) Kafka Streams crashes after ProducerFencedException

[ https://issues.apache.org/jira/browse/KAFKA-14567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna updated KAFKA-14567: -- Affects Version/s: 3.7.0 (was: 3.8.0) > Kafka Streams crashes

[jira] [Assigned] (KAFKA-14567) Kafka Streams crashes after ProducerFencedException

[ https://issues.apache.org/jira/browse/KAFKA-14567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna reassigned KAFKA-14567: - Assignee: Kirk True > Kafka Streams crashes after ProducerFencedException >

[jira] [Updated] (KAFKA-14567) Kafka Streams crashes after ProducerFencedException

[ https://issues.apache.org/jira/browse/KAFKA-14567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna updated KAFKA-14567: -- Priority: Blocker (was: Major) > Kafka Streams crashes after ProducerFencedException >

[jira] [Updated] (KAFKA-14567) Kafka Streams crashes after ProducerFencedException

[ https://issues.apache.org/jira/browse/KAFKA-14567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna updated KAFKA-14567: -- Affects Version/s: 3.8.0 > Kafka Streams crashes after ProducerFencedException >

[jira] [Commented] (KAFKA-16514) Kafka Streams: stream.close(CloseOptions) does not respect options.leaveGroup flag.

[ https://issues.apache.org/jira/browse/KAFKA-16514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17839613#comment-17839613 ] Bruno Cadonna commented on KAFKA-16514: --- I might have missed this, but why can we not just

[jira] [Commented] (KAFKA-16567) Add New Stream Metrics based on KIP-869

[ https://issues.apache.org/jira/browse/KAFKA-16567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17839601#comment-17839601 ] Bruno Cadonna commented on KAFKA-16567: --- I think as long as we do not enable the state updater by

[jira] [Reopened] (KAFKA-15538) Client support for java regex based subscription

[ https://issues.apache.org/jira/browse/KAFKA-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna reopened KAFKA-15538: --- > Client support for java regex based subscription >

[jira] [Closed] (KAFKA-16224) Fix handling of deleted topic when auto-committing before revocation

[ https://issues.apache.org/jira/browse/KAFKA-16224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna closed KAFKA-16224. - > Fix handling of deleted topic when auto-committing before revocation >

[jira] [Commented] (KAFKA-16403) Flaky test org.apache.kafka.streams.examples.wordcount.WordCountDemoTest.testCountListOfWords

[ https://issues.apache.org/jira/browse/KAFKA-16403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829826#comment-17829826 ] Bruno Cadonna commented on KAFKA-16403: --- I would think so since we have never encountered this

[jira] [Commented] (KAFKA-16403) Flaky test org.apache.kafka.streams.examples.wordcount.WordCountDemoTest.testCountListOfWords

[ https://issues.apache.org/jira/browse/KAFKA-16403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829824#comment-17829824 ] Bruno Cadonna commented on KAFKA-16403: --- Thanks for the report [~soarez]! Can you reproduce this

[jira] [Closed] (KAFKA-16227) Console consumer fails with `IllegalStateException`

[ https://issues.apache.org/jira/browse/KAFKA-16227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna closed KAFKA-16227. - > Console consumer fails with `IllegalStateException` >

[jira] [Assigned] (KAFKA-16350) StateUpdater does not init transaction after canceling task close action

[ https://issues.apache.org/jira/browse/KAFKA-16350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna reassigned KAFKA-16350: - Assignee: Bruno Cadonna > StateUpdater does not init transaction after canceling task

[jira] [Commented] (KAFKA-16350) StateUpdater does not init transaction after canceling task close action

[ https://issues.apache.org/jira/browse/KAFKA-16350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17825278#comment-17825278 ] Bruno Cadonna commented on KAFKA-16350: --- Thanks for the report [~mjsax]! I think the bug is in

[jira] [Closed] (KAFKA-16285) Make group metadata available when a new assignment is set in async Kafka consumer

[ https://issues.apache.org/jira/browse/KAFKA-16285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna closed KAFKA-16285. - > Make group metadata available when a new assignment is set in async Kafka > consumer >

[jira] [Reopened] (KAFKA-10199) Separate state restoration into separate threads

[ https://issues.apache.org/jira/browse/KAFKA-10199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna reopened KAFKA-10199: --- > Separate state restoration into separate threads >

[jira] [Updated] (KAFKA-10199) Separate state restoration into separate threads

[ https://issues.apache.org/jira/browse/KAFKA-10199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna updated KAFKA-10199: -- Fix Version/s: 3.8.0 (was: 3.7.0) > Separate state restoration into

[jira] [Commented] (KAFKA-16290) Investigate propagating subscription state updates via queues

[ https://issues.apache.org/jira/browse/KAFKA-16290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17822250#comment-17822250 ] Bruno Cadonna commented on KAFKA-16290: --- I changed the version to 4.0.0. > Investigate

[jira] [Updated] (KAFKA-16290) Investigate propagating subscription state updates via queues

[ https://issues.apache.org/jira/browse/KAFKA-16290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna updated KAFKA-16290: -- Fix Version/s: 4.0.0 (was: 3.8.0) > Investigate propagating

[jira] [Commented] (KAFKA-9062) Handle stalled writes to RocksDB

[ https://issues.apache.org/jira/browse/KAFKA-9062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821066#comment-17821066 ] Bruno Cadonna commented on KAFKA-9062: -- Closed it. If we will run again into a similar issue let's

[jira] [Resolved] (KAFKA-9062) Handle stalled writes to RocksDB

[ https://issues.apache.org/jira/browse/KAFKA-9062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna resolved KAFKA-9062. -- Resolution: Won't Fix > Handle stalled writes to RocksDB > >

[jira] [Closed] (KAFKA-15555) Ensure wakeups are handled correctly in PrototypeAsyncConsumer.poll()

[ https://issues.apache.org/jira/browse/KAFKA-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna closed KAFKA-1. - > Ensure wakeups are handled correctly in PrototypeAsyncConsumer.poll() >

[jira] [Closed] (KAFKA-16194) KafkaConsumer.groupMetadata() should be correct when first records are returned

[ https://issues.apache.org/jira/browse/KAFKA-16194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna closed KAFKA-16194. - > KafkaConsumer.groupMetadata() should be correct when first records are > returned >

[jira] [Closed] (KAFKA-15991) Flaky new consumer test testGroupIdNotNullAndValid

[ https://issues.apache.org/jira/browse/KAFKA-15991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna closed KAFKA-15991. - > Flaky new consumer test testGroupIdNotNullAndValid >

[jira] [Resolved] (KAFKA-16194) KafkaConsumer.groupMetadata() should be correct when first records are returned

[ https://issues.apache.org/jira/browse/KAFKA-16194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna resolved KAFKA-16194. --- Resolution: Fixed > KafkaConsumer.groupMetadata() should be correct when first records are

[jira] [Updated] (KAFKA-16285) Make group metadata available when a new assignment is set in async Kafka consumer

[ https://issues.apache.org/jira/browse/KAFKA-16285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna updated KAFKA-16285: -- Description: Currently, the new async Kafka consumer sends an event from the background

[jira] [Created] (KAFKA-16285) Make group metadata available when a new assignment is set in async Kafka consumer

Bruno Cadonna created KAFKA-16285: - Summary: Make group metadata available when a new assignment is set in async Kafka consumer Key: KAFKA-16285 URL: https://issues.apache.org/jira/browse/KAFKA-16285

[jira] [Assigned] (KAFKA-16139) StreamsUpgradeTest fails consistently in 3.7.0

[ https://issues.apache.org/jira/browse/KAFKA-16139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna reassigned KAFKA-16139: - Assignee: Bruno Cadonna > StreamsUpgradeTest fails consistently in 3.7.0 >

[jira] [Commented] (KAFKA-16139) StreamsUpgradeTest fails consistently in 3.7.0

[ https://issues.apache.org/jira/browse/KAFKA-16139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17807174#comment-17807174 ] Bruno Cadonna commented on KAFKA-16139: --- Note that since

[jira] [Resolved] (KAFKA-16098) State updater may attempt to resume a task that is not assigned anymore

[ https://issues.apache.org/jira/browse/KAFKA-16098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna resolved KAFKA-16098. --- Resolution: Fixed > State updater may attempt to resume a task that is not assigned anymore

[jira] [Commented] (KAFKA-9545) Flaky Test `RegexSourceIntegrationTest.testRegexMatchesTopicsAWhenDeleted`

[ https://issues.apache.org/jira/browse/KAFKA-9545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17805126#comment-17805126 ] Bruno Cadonna commented on KAFKA-9545: -- [~ashwinpankaj] Thank you for verifying the flakiness!

[jira] [Assigned] (KAFKA-16098) State updater may attempt to resume a task that is not assigned anymore

[ https://issues.apache.org/jira/browse/KAFKA-16098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna reassigned KAFKA-16098: - Assignee: Bruno Cadonna > State updater may attempt to resume a task that is not

[jira] [Updated] (KAFKA-16017) Checkpointed offset is incorrect when task is revived and restoring

[ https://issues.apache.org/jira/browse/KAFKA-16017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna updated KAFKA-16017: -- Fix Version/s: 3.7.0 > Checkpointed offset is incorrect when task is revived and restoring >

[jira] [Resolved] (KAFKA-15991) Flaky new consumer test testGroupIdNotNullAndValid

[ https://issues.apache.org/jira/browse/KAFKA-15991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna resolved KAFKA-15991. --- Resolution: Fixed > Flaky new consumer test testGroupIdNotNullAndValid >

[jira] [Updated] (KAFKA-15991) Flaky new consumer test testGroupIdNotNullAndValid

[ https://issues.apache.org/jira/browse/KAFKA-15991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna updated KAFKA-15991: -- Fix Version/s: 3.7.0 (was: 3.8.0) > Flaky new consumer test

[jira] [Commented] (KAFKA-15991) Flaky new consumer test testGroupIdNotNullAndValid

[ https://issues.apache.org/jira/browse/KAFKA-15991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799019#comment-17799019 ] Bruno Cadonna commented on KAFKA-15991: --- This is resolved via

[jira] [Updated] (KAFKA-16017) Checkpointed offset is incorrect when task is revived and restoring

[ https://issues.apache.org/jira/browse/KAFKA-16017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna updated KAFKA-16017: -- Description: Streams checkpoints the wrong offset when a task is revived after a

[jira] [Updated] (KAFKA-16017) Checkpointed offset is incorrect when task is revived and restoring

[ https://issues.apache.org/jira/browse/KAFKA-16017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna updated KAFKA-16017: -- Description: Streams checkpoints the wrong offset when a task is revived after a

[jira] [Assigned] (KAFKA-16017) Checkpointed offset is incorrect when task is revived and restoring

[ https://issues.apache.org/jira/browse/KAFKA-16017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna reassigned KAFKA-16017: - Assignee: Bruno Cadonna > Checkpointed offset is incorrect when task is revived and

[jira] [Updated] (KAFKA-16017) Checkpointed offset is incorrect when task is revived and restoring

[ https://issues.apache.org/jira/browse/KAFKA-16017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna updated KAFKA-16017: -- Description: Streams checkpoints the wrong offset when a task is revived after a

[jira] [Updated] (KAFKA-16017) Checkpointed offset is incorrect when task is revived and restoring

[ https://issues.apache.org/jira/browse/KAFKA-16017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna updated KAFKA-16017: -- Description: Streams checkpoints the wrong offset when a task is revived after a

[jira] [Created] (KAFKA-16017) Checkpointed offset is incorrect when task is revived and restoring

Bruno Cadonna created KAFKA-16017: - Summary: Checkpointed offset is incorrect when task is revived and restoring Key: KAFKA-16017 URL: https://issues.apache.org/jira/browse/KAFKA-16017 Project:

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

[ https://issues.apache.org/jira/browse/KAFKA-14454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796101#comment-17796101 ] Bruno Cadonna commented on KAFKA-14454: --- [~sagarrao] First of all my apologies! I didn't look at

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

[ https://issues.apache.org/jira/browse/KAFKA-14454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796079#comment-17796079 ] Bruno Cadonna commented on KAFKA-14454: --- [~sagarrao] Was the error: {code:java}

[jira] [Commented] (KAFKA-9545) Flaky Test `RegexSourceIntegrationTest.testRegexMatchesTopicsAWhenDeleted`

[ https://issues.apache.org/jira/browse/KAFKA-9545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796053#comment-17796053 ] Bruno Cadonna commented on KAFKA-9545: -- I am reopening this issue, because

[jira] [Reopened] (KAFKA-9545) Flaky Test `RegexSourceIntegrationTest.testRegexMatchesTopicsAWhenDeleted`

[ https://issues.apache.org/jira/browse/KAFKA-9545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna reopened KAFKA-9545: -- > Flaky Test `RegexSourceIntegrationTest.testRegexMatchesTopicsAWhenDeleted` >

[jira] [Assigned] (KAFKA-15991) Flaky new consumer test testGroupIdNotNullAndValid

[ https://issues.apache.org/jira/browse/KAFKA-15991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna reassigned KAFKA-15991: - Assignee: Bruno Cadonna > Flaky new consumer test testGroupIdNotNullAndValid >

[jira] [Commented] (KAFKA-15991) Flaky new consumer test testGroupIdNotNullAndValid

[ https://issues.apache.org/jira/browse/KAFKA-15991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795221#comment-17795221 ] Bruno Cadonna commented on KAFKA-15991: --- Thanks for the ticket [~lianetm]! I have a

[jira] [Assigned] (KAFKA-14438) Throw error when consumer configured with empty/whitespace-only group.id for AsyncKafkaConsumer

[ https://issues.apache.org/jira/browse/KAFKA-14438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna reassigned KAFKA-14438: - Assignee: Bruno Cadonna (was: Kirk True) > Throw error when consumer configured with

[jira] [Resolved] (KAFKA-14438) Throw error when consumer configured with empty/whitespace-only group.id for AsyncKafkaConsumer

[ https://issues.apache.org/jira/browse/KAFKA-14438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna resolved KAFKA-14438. --- Resolution: Fixed > Throw error when consumer configured with empty/whitespace-only

[jira] [Commented] (KAFKA-15798) Flaky Test NamedTopologyIntegrationTest.shouldAddAndRemoveNamedTopologiesBeforeStartingAndRouteQueriesToCorrectTopology()

[ https://issues.apache.org/jira/browse/KAFKA-15798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17789958#comment-17789958 ] Bruno Cadonna commented on KAFKA-15798: --- [~ableegoldman] Thanks for looking into this! I actually

[jira] [Resolved] (KAFKA-15555) Ensure wakeups are handled correctly in PrototypeAsyncConsumer.poll()

[ https://issues.apache.org/jira/browse/KAFKA-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna resolved KAFKA-1. --- Resolution: Fixed > Ensure wakeups are handled correctly in PrototypeAsyncConsumer.poll() >

[jira] [Assigned] (KAFKA-15281) Implement the groupMetadata Consumer API

[ https://issues.apache.org/jira/browse/KAFKA-15281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna reassigned KAFKA-15281: - Assignee: Bruno Cadonna (was: Kirk True) > Implement the groupMetadata Consumer API >

[jira] [Commented] (KAFKA-15865) Ensure consumer.poll() execute autocommit callback

[ https://issues.apache.org/jira/browse/KAFKA-15865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17788376#comment-17788376 ] Bruno Cadonna commented on KAFKA-15865: --- This seems to be blocked on KAFKA-15327 since

[jira] [Updated] (KAFKA-15765) Remove task level metric "commit-latency"

[ https://issues.apache.org/jira/browse/KAFKA-15765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna updated KAFKA-15765: -- Fix Version/s: 3.7.0 (was: 4.0.0) > Remove task level metric

[jira] [Updated] (KAFKA-15765) Remove task level metric "commit-latency"

[ https://issues.apache.org/jira/browse/KAFKA-15765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna updated KAFKA-15765: -- Priority: Major (was: Blocker) > Remove task level metric "commit-latency" >

[jira] [Updated] (KAFKA-15624) Reconsider synchronisation of methods in RocksDBStore

[ https://issues.apache.org/jira/browse/KAFKA-15624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna updated KAFKA-15624: -- Component/s: streams > Reconsider synchronisation of methods in RocksDBStore >

[jira] [Updated] (KAFKA-15624) Reconsider synchronisation of methods in RocksDBStore

[ https://issues.apache.org/jira/browse/KAFKA-15624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna updated KAFKA-15624: -- Labels: (was: streams) > Reconsider synchronisation of methods in RocksDBStore >

[jira] [Created] (KAFKA-15625) Do not flush global state store at each commit

Bruno Cadonna created KAFKA-15625: - Summary: Do not flush global state store at each commit Key: KAFKA-15625 URL: https://issues.apache.org/jira/browse/KAFKA-15625 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-15624) Reconsider synchronisation of methods in RocksDBStore

Bruno Cadonna created KAFKA-15624: - Summary: Reconsider synchronisation of methods in RocksDBStore Key: KAFKA-15624 URL: https://issues.apache.org/jira/browse/KAFKA-15624 Project: Kafka

[jira] [Resolved] (KAFKA-15577) Reload4j | CVE-2022-45868

[ https://issues.apache.org/jira/browse/KAFKA-15577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna resolved KAFKA-15577. --- Resolution: Not A Problem > Reload4j | CVE-2022-45868 > - > >

[jira] [Commented] (KAFKA-15577) Reload4j | CVE-2022-45868

[ https://issues.apache.org/jira/browse/KAFKA-15577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17773985#comment-17773985 ] Bruno Cadonna commented on KAFKA-15577: --- The vulnerability is in the H2 database engine and not

[jira] [Updated] (KAFKA-10199) Separate state restoration into separate threads

[ https://issues.apache.org/jira/browse/KAFKA-10199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna updated KAFKA-10199: -- Fix Version/s: 3.7.0 > Separate state restoration into separate threads >

[jira] [Resolved] (KAFKA-10199) Separate state restoration into separate threads

[ https://issues.apache.org/jira/browse/KAFKA-10199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna resolved KAFKA-10199. --- Resolution: Done > Separate state restoration into separate threads >

[jira] [Updated] (KAFKA-13973) block-cache-capacity metrics worth twice as much as normal

[ https://issues.apache.org/jira/browse/KAFKA-13973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna updated KAFKA-13973: -- Fix Version/s: 3.7.0 > block-cache-capacity metrics worth twice as much as normal >

[jira] [Resolved] (KAFKA-13973) block-cache-capacity metrics worth twice as much as normal

[ https://issues.apache.org/jira/browse/KAFKA-13973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna resolved KAFKA-13973. --- Resolution: Fixed > block-cache-capacity metrics worth twice as much as normal >

[jira] [Assigned] (KAFKA-13973) block-cache-capacity metrics worth twice as much as normal

[ https://issues.apache.org/jira/browse/KAFKA-13973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna reassigned KAFKA-13973: - Assignee: Nicholas Telford > block-cache-capacity metrics worth twice as much as

[jira] [Commented] (KAFKA-15463) StreamsException: Accessing from an unknown node

[ https://issues.apache.org/jira/browse/KAFKA-15463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17765066#comment-17765066 ] Bruno Cadonna commented on KAFKA-15463: --- [~yevsh] Sorry to hear that you have issues! Could you

[jira] [Commented] (KAFKA-15443) Upgrade RocksDB dependency

[ https://issues.apache.org/jira/browse/KAFKA-15443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17762984#comment-17762984 ] Bruno Cadonna commented on KAFKA-15443: --- As always we also need to verify the API compatibility --

[jira] [Resolved] (KAFKA-15319) Upgrade rocksdb to fix CVE-2022-37434

[ https://issues.apache.org/jira/browse/KAFKA-15319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna resolved KAFKA-15319. --- Resolution: Fixed > Upgrade rocksdb to fix CVE-2022-37434 >

[jira] [Commented] (KAFKA-15297) Cache flush order might not be topological order

[ https://issues.apache.org/jira/browse/KAFKA-15297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751932#comment-17751932 ] Bruno Cadonna commented on KAFKA-15297: --- [~guozhang] Yes, I agree the issue is when state stores

[jira] [Updated] (KAFKA-15297) Cache flush order might not be topological order

[ https://issues.apache.org/jira/browse/KAFKA-15297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna updated KAFKA-15297: -- Description: The flush order of the state store caches in Kafka Streams might not correspond

[jira] [Comment Edited] (KAFKA-15297) Cache flush order might not be topological order

[ https://issues.apache.org/jira/browse/KAFKA-15297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17750622#comment-17750622 ] Bruno Cadonna edited comment on KAFKA-15297 at 8/3/23 8:10 AM: ---

[jira] [Comment Edited] (KAFKA-15297) Cache flush order might not be topological order

[ https://issues.apache.org/jira/browse/KAFKA-15297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17750622#comment-17750622 ] Bruno Cadonna edited comment on KAFKA-15297 at 8/3/23 8:09 AM: ---

[jira] [Updated] (KAFKA-15297) Cache flush order might not be topological order

[ https://issues.apache.org/jira/browse/KAFKA-15297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna updated KAFKA-15297: -- Description: The flush order of the state store caches in Kafka Streams might not correspond

[jira] [Commented] (KAFKA-15297) Cache flush order might not be topological order

[ https://issues.apache.org/jira/browse/KAFKA-15297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17750622#comment-17750622 ] Bruno Cadonna commented on KAFKA-15297: --- [~ableegoldman] You can observe the flush order by

[jira] [Updated] (KAFKA-15297) Cache flush order might not be topological order

[ https://issues.apache.org/jira/browse/KAFKA-15297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna updated KAFKA-15297: -- Description: The flush order of the state store caches in Kafka Streams might not correspond

[jira] [Updated] (KAFKA-15297) Cache flush order might not be topological order

[ https://issues.apache.org/jira/browse/KAFKA-15297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna updated KAFKA-15297: -- Description: The flush order of the state store caches in Kafka Streams might not correspond

[jira] [Updated] (KAFKA-15297) Cache flush order might not be topological order

[ https://issues.apache.org/jira/browse/KAFKA-15297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna updated KAFKA-15297: -- Description: The flush order of the state store caches in Kafka Streams might not correspond

[jira] [Updated] (KAFKA-15297) Cache flush order might not be topological order

[ https://issues.apache.org/jira/browse/KAFKA-15297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna updated KAFKA-15297: -- Description: The flush order of the state store caches in Kafka Streams might not correspond

[jira] [Created] (KAFKA-15297) Cache flush order might not be topological order

Bruno Cadonna created KAFKA-15297: - Summary: Cache flush order might not be topological order Key: KAFKA-15297 URL: https://issues.apache.org/jira/browse/KAFKA-15297 Project: Kafka Issue

[jira] [Updated] (KAFKA-15297) Cache flush order might not be topological order

[ https://issues.apache.org/jira/browse/KAFKA-15297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna updated KAFKA-15297: -- Attachment: minimal_example.png > Cache flush order might not be topological order >

[jira] [Commented] (KAFKA-15193) Allow choosing Platform specific rocksDBJNI jar

[ https://issues.apache.org/jira/browse/KAFKA-15193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17743865#comment-17743865 ] Bruno Cadonna commented on KAFKA-15193: --- This reduction would only apply to Kafka Streams users,

[jira] [Commented] (KAFKA-15193) Allow choosing Platform specific rocksDBJNI jar

[ https://issues.apache.org/jira/browse/KAFKA-15193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17743711#comment-17743711 ] Bruno Cadonna commented on KAFKA-15193: --- Hi Utkarsh, Thanks for the ticket! Wouldn't it be simpler

[jira] [Commented] (KAFKA-15187) Add headers to partition method.

[ https://issues.apache.org/jira/browse/KAFKA-15187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17742814#comment-17742814 ] Bruno Cadonna commented on KAFKA-15187: --- In the PR, I see that you want to change the

[jira] [Commented] (KAFKA-15187) Add headers to partition method.

[ https://issues.apache.org/jira/browse/KAFKA-15187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17742812#comment-17742812 ] Bruno Cadonna commented on KAFKA-15187: --- I added you to the contributor group. Now you should be

[jira] [Commented] (KAFKA-12679) Rebalancing a restoring or running task may cause directory livelocking with newly created task

[ https://issues.apache.org/jira/browse/KAFKA-12679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17732032#comment-17732032 ] Bruno Cadonna commented on KAFKA-12679: --- [~Andras Hatvani] Lucas' PR solves the issue for the

[jira] [Commented] (KAFKA-15072) Flaky test MirrorConnectorsIntegrationExactlyOnceTest.testReplicationWithEmptyPartition

[ https://issues.apache.org/jira/browse/KAFKA-15072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17731529#comment-17731529 ] Bruno Cadonna commented on KAFKA-15072: --- I encountered a failure of

[jira] [Commented] (KAFKA-15052) Fix flaky test QuorumControllerTest.testBalancePartitionLeaders()

[ https://issues.apache.org/jira/browse/KAFKA-15052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17731528#comment-17731528 ] Bruno Cadonna commented on KAFKA-15052: --- I also encountered this here:

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

[ https://issues.apache.org/jira/browse/KAFKA-15020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17731526#comment-17731526 ] Bruno Cadonna commented on KAFKA-15020: --- I encountered the same build failure as [~jlprat]

[jira] [Commented] (KAFKA-15072) Flaky test MirrorConnectorsIntegrationExactlyOnceTest.testReplicationWithEmptyPartition

[ https://issues.apache.org/jira/browse/KAFKA-15072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17731344#comment-17731344 ] Bruno Cadonna commented on KAFKA-15072: --- I also see the following test that fail with the same

[jira] [Comment Edited] (KAFKA-15072) Flaky test MirrorConnectorsIntegrationExactlyOnceTest.testReplicationWithEmptyPartition

[ https://issues.apache.org/jira/browse/KAFKA-15072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17731344#comment-17731344 ] Bruno Cadonna edited comment on KAFKA-15072 at 6/11/23 1:05 PM: I also

[jira] [Commented] (KAFKA-14981) Set `group.instance.id` in streams consumer so that rebalance will not happen if a instance is restarted

[ https://issues.apache.org/jira/browse/KAFKA-14981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727427#comment-17727427 ] Bruno Cadonna commented on KAFKA-14981: --- I have the same feeling as [~ableegoldman]. So, we should

[jira] [Commented] (KAFKA-14922) kafka-streams-application-reset deletes topics not belonging to specified application-id

[ https://issues.apache.org/jira/browse/KAFKA-14922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17714484#comment-17714484 ] Bruno Cadonna commented on KAFKA-14922: --- I see. We could add a warning with the list of internal

[jira] [Resolved] (KAFKA-12634) Should checkpoint after restore finished

[ https://issues.apache.org/jira/browse/KAFKA-12634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna resolved KAFKA-12634. --- Resolution: Fixed > Should checkpoint after restore finished >

  1   2   3   4   5   6   7   8   9   10   >