[
https://issues.apache.org/jira/browse/KAFKA-17112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17865978#comment-17865978
]
Bruno Cadonna commented on KAFKA-17112:
---
[~aoli-al] I think a quick fix to get rid of the leaked
[
https://issues.apache.org/jira/browse/KAFKA-17112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17865670#comment-17865670
]
Bruno Cadonna commented on KAFKA-17112:
---
[~aoli-al] Yes, but I guess they are only expected to be
[
https://issues.apache.org/jira/browse/KAFKA-17112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17865553#comment-17865553
]
Bruno Cadonna commented on KAFKA-17112:
---
[~aoli-al] I think it would be better to change where the
[
https://issues.apache.org/jira/browse/KAFKA-17112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17865048#comment-17865048
]
Bruno Cadonna commented on KAFKA-17112:
---
[~aoli-al] I think you are right. We are leaking the
[
https://issues.apache.org/jira/browse/KAFKA-17098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17864987#comment-17864987
]
Bruno Cadonna commented on KAFKA-17098:
---
[~eduwerc] I think, I found the issue. See the attached
[
https://issues.apache.org/jira/browse/KAFKA-17098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Cadonna reassigned KAFKA-17098:
-
Assignee: Bruno Cadonna
> Error Opening RocksDBStore
> --
>
>
[
https://issues.apache.org/jira/browse/KAFKA-17098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Cadonna updated KAFKA-17098:
--
Priority: Critical (was: Minor)
> Error Opening RocksDBStore
> --
>
[
https://issues.apache.org/jira/browse/KAFKA-9738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17864948#comment-17864948
]
Bruno Cadonna commented on KAFKA-9738:
--
The old `MockProcessorContext` is still not deprecated,
Bruno Cadonna created KAFKA-17109:
-
Summary: Reduce log message load for failed locking
Key: KAFKA-17109
URL: https://issues.apache.org/jira/browse/KAFKA-17109
Project: Kafka
Issue Type:
[
https://issues.apache.org/jira/browse/KAFKA-17085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Cadonna reassigned KAFKA-17085:
-
Assignee: Bruno Cadonna (was: Matthias J. Sax)
> Streams Cooperative Rebalance
[
https://issues.apache.org/jira/browse/KAFKA-17098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17864077#comment-17864077
]
Bruno Cadonna commented on KAFKA-17098:
---
Apparently, my fix does not fix this issue. [~eduwerc]
[
https://issues.apache.org/jira/browse/KAFKA-13295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Cadonna resolved KAFKA-13295.
---
Fix Version/s: 3.8.0
Resolution: Fixed
> Long restoration times for new tasks can
[
https://issues.apache.org/jira/browse/KAFKA-13295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Cadonna updated KAFKA-13295:
--
Fix Version/s: (was: 3.8.0)
> Long restoration times for new tasks can lead to
[
https://issues.apache.org/jira/browse/KAFKA-13295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Cadonna updated KAFKA-13295:
--
Fix Version/s: 3.8.0
> Long restoration times for new tasks can lead to transaction timeouts
[
https://issues.apache.org/jira/browse/KAFKA-8812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Cadonna reassigned KAFKA-8812:
Assignee: (was: Bruno Cadonna)
> Rebalance Producers
> ---
>
>
[
https://issues.apache.org/jira/browse/KAFKA-8812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Cadonna reassigned KAFKA-8812:
Assignee: Bruno Cadonna
> Rebalance Producers
> ---
>
>
[
https://issues.apache.org/jira/browse/KAFKA-14567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17855536#comment-17855536
]
Bruno Cadonna commented on KAFKA-14567:
---
[~ableegoldman] We ([~mjsax] and I) discussed it and came
[
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.9.0
(was: 3.8.0)
> Kafka Streams crashes after
[
https://issues.apache.org/jira/browse/KAFKA-14567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Cadonna reopened KAFKA-14567:
---
> Kafka Streams crashes after ProducerFencedException
>
[
https://issues.apache.org/jira/browse/KAFKA-14567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853994#comment-17853994
]
Bruno Cadonna commented on KAFKA-14567:
---
I reopen this ticket since I found the issue in our
[
https://issues.apache.org/jira/browse/KAFKA-14567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853611#comment-17853611
]
Bruno Cadonna commented on KAFKA-14567:
---
[~mjsax] I am not completely sure, but it could be. The
[
https://issues.apache.org/jira/browse/KAFKA-16903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853602#comment-17853602
]
Bruno Cadonna commented on KAFKA-16903:
---
[~ableegoldman] I actually do not know. I found it on
Bruno Cadonna created KAFKA-16903:
-
Summary: Task should consider producer error previously occurred
for different task
Key: KAFKA-16903
URL: https://issues.apache.org/jira/browse/KAFKA-16903
[
https://issues.apache.org/jira/browse/KAFKA-13295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Cadonna reassigned KAFKA-13295:
-
Assignee: Bruno Cadonna
> Long restoration times for new tasks can lead to transaction
[
https://issues.apache.org/jira/browse/KAFKA-13295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850702#comment-17850702
]
Bruno Cadonna commented on KAFKA-13295:
---
I re-opened the issue because we did not release the
[
https://issues.apache.org/jira/browse/KAFKA-13295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Cadonna updated KAFKA-13295:
--
Fix Version/s: (was: 3.4.0)
> Long restoration times for new tasks can lead to
[
https://issues.apache.org/jira/browse/KAFKA-13295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Cadonna reopened KAFKA-13295:
---
Assignee: (was: Sagar Rao)
> Long restoration times for new tasks can lead to
[
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
[
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:
[
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
[
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
[
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
[
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
>
[
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
[
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
>
[
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
>
[
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
>
[
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
[
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
[
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
>
[
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
>
[
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
[
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
[
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`
>
[
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
[
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
[
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
>
[
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
>
[
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
[
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
[
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
[
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
[
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
>
>
[
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()
>
[
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
>
[
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
>
[
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
[
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
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
[
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
>
[
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
[
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
[
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!
[
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
[
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
>
[
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
>
[
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
[
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
[
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
[
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
[
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
[
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
[
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
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:
[
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
[
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}
[
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
[
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`
>
[
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
>
[
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
[
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
[
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
[
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
[
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()
>
[
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
>
[
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
[
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
[
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"
>
[
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
>
[
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
>
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:
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
[
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
> -
>
>
[
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
[
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
>
[
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
>
[
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
>
[
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
>
[
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
[
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
1 - 100 of 991 matches
Mail list logo
