[
https://issues.apache.org/jira/browse/KAFKA-17584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Cadonna updated KAFKA-17584:
--
Affects Version/s: 3.9.0
> Changing dynamic configurations resets retention
>
[
https://issues.apache.org/jira/browse/KAFKA-17489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Cadonna resolved KAFKA-17489.
---
Resolution: Fixed
> IllegalStateException if failed task is removed from state updater
> ---
[
https://issues.apache.org/jira/browse/KAFKA-17489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Cadonna updated KAFKA-17489:
--
Affects Version/s: 3.9.0
> IllegalStateException if failed task is removed from state updater
[
https://issues.apache.org/jira/browse/KAFKA-16332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17878740#comment-17878740
]
Bruno Cadonna commented on KAFKA-16332:
---
[~mjsax] What would be the alternative? T
[
https://issues.apache.org/jira/browse/KAFKA-17462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Cadonna updated KAFKA-17462:
--
Labels: needs-kip (was: )
> Removes intermediateTopicsOption from StreamsResetter
> -
[
https://issues.apache.org/jira/browse/KAFKA-17446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17878040#comment-17878040
]
Bruno Cadonna commented on KAFKA-17446:
---
[~rohitbobade] Could you please share som
[
https://issues.apache.org/jira/browse/KAFKA-17445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17878006#comment-17878006
]
Bruno Cadonna commented on KAFKA-17445:
---
[~rohitbobade] It is not clear to me what
[
https://issues.apache.org/jira/browse/KAFKA-16567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17876631#comment-17876631
]
Bruno Cadonna commented on KAFKA-16567:
---
[~balajirrao] Thank you for pointing that
[
https://issues.apache.org/jira/browse/KAFKA-14438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Cadonna closed KAFKA-14438.
-
> Throw error when consumer configured with empty/whitespace-only group.id for
> AsyncKafkaConsumer
[
https://issues.apache.org/jira/browse/KAFKA-17324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17873155#comment-17873155
]
Bruno Cadonna commented on KAFKA-17324:
---
Yeah, exactly! The EOS overrides are just
[
https://issues.apache.org/jira/browse/KAFKA-17324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17873144#comment-17873144
]
Bruno Cadonna commented on KAFKA-17324:
---
Yes, please assign the ticket to yourself
Bruno Cadonna created KAFKA-17324:
-
Summary: Set config {{group.protocol}} to {{classic}} in Streams
Key: KAFKA-17324
URL: https://issues.apache.org/jira/browse/KAFKA-17324
Project: Kafka
Iss
[
https://issues.apache.org/jira/browse/KAFKA-17324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Cadonna updated KAFKA-17324:
--
Summary: Set config group.protocol to classic in Streams (was: Set config
{{group.protocol}}
[
https://issues.apache.org/jira/browse/KAFKA-16442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17873123#comment-17873123
]
Bruno Cadonna commented on KAFKA-16442:
---
[~kirktrue] Streams cannot be used with K
[
https://issues.apache.org/jira/browse/KAFKA-16441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17873125#comment-17873125
]
Bruno Cadonna commented on KAFKA-16441:
---
[~kirktrue] Streams cannot be used with K
[
https://issues.apache.org/jira/browse/KAFKA-16443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17873124#comment-17873124
]
Bruno Cadonna commented on KAFKA-16443:
---
[~kirktrue] Streams cannot be used with K
[
https://issues.apache.org/jira/browse/KAFKA-16567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Cadonna updated KAFKA-16567:
--
Description:
Add the following metrics to the state updater:
* restore-total
* restore-rate
*
[
https://issues.apache.org/jira/browse/KAFKA-16567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17873018#comment-17873018
]
Bruno Cadonna commented on KAFKA-16567:
---
I verified the metrics listed in this tic
[
https://issues.apache.org/jira/browse/KAFKA-17112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865978#comment-17865978
]
Bruno Cadonna commented on KAFKA-17112:
---
[~aoli-al] I think a quick fix to get rid
[
https://issues.apache.org/jira/browse/KAFKA-17112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865670#comment-17865670
]
Bruno Cadonna commented on KAFKA-17112:
---
[~aoli-al] Yes, but I guess they are only
[
https://issues.apache.org/jira/browse/KAFKA-17112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865553#comment-17865553
]
Bruno Cadonna commented on KAFKA-17112:
---
[~aoli-al] I think it would be better to
[
https://issues.apache.org/jira/browse/KAFKA-17112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865048#comment-17865048
]
Bruno Cadonna commented on KAFKA-17112:
---
[~aoli-al] I think you are right. We are
[
https://issues.apache.org/jira/browse/KAFKA-17098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864987#comment-17864987
]
Bruno Cadonna commented on KAFKA-17098:
---
[~eduwerc] I think, I found the issue. Se
[
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&focusedCommentId=17864948#comment-17864948
]
Bruno Cadonna commented on KAFKA-9738:
--
The old `MockProcessorContext` is still not
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: Impr
[
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 Upgrade
[
https://issues.apache.org/jira/browse/KAFKA-17098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864077#comment-17864077
]
Bruno Cadonna commented on KAFKA-17098:
---
Apparently, my fix does not fix this issu
[
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 lea
[
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 transaction
[
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
> ---
>
> Ke
[
https://issues.apache.org/jira/browse/KAFKA-14567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17855536#comment-17855536
]
Bruno Cadonna commented on KAFKA-14567:
---
[~ableegoldman] We ([~mjsax] and I) discu
[
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 Produce
[
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&focusedCommentId=17853994#comment-17853994
]
Bruno Cadonna commented on KAFKA-14567:
---
I reopen this ticket since I found the is
[
https://issues.apache.org/jira/browse/KAFKA-14567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17853611#comment-17853611
]
Bruno Cadonna commented on KAFKA-14567:
---
[~mjsax] I am not completely sure, but it
[
https://issues.apache.org/jira/browse/KAFKA-16903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17853602#comment-17853602
]
Bruno Cadonna commented on KAFKA-16903:
---
[~ableegoldman] I actually do not know. I
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
Project:
[
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&focusedCommentId=17850702#comment-17850702
]
Bruno Cadonna commented on KAFKA-13295:
---
I re-opened the issue because we did not
[
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 transaction
[
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 transact
[
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 action
[
https://issues.apache.org/jira/browse/KAFKA-16350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17847008#comment-17847008
]
Bruno Cadonna commented on KAFKA-16350:
---
This issue should be gone after the follo
[
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 StreamThreadTest#shouldCloseAllTaskProducersOnClose
[
https://issues.apache.org/jira/browse/KAFKA-16774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17846959#comment-17846959
]
Bruno Cadonna commented on KAFKA-16774:
---
Looking at the test, I think we can remov
[
https://issues.apache.org/jira/browse/KAFKA-16774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17846940#comment-17846940
]
Bruno Cadonna commented on KAFKA-16774:
---
[~chia7712] Thank you for your analysis!
[
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 after
[
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&focusedCommentId=17839613#comment-17839613
]
Bruno Cadonna commented on KAFKA-16514:
---
I might have missed this, but why can we
[
https://issues.apache.org/jira/browse/KAFKA-16567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17839601#comment-17839601
]
Bruno Cadonna commented on KAFKA-16567:
---
I think as long as we do not enable the s
[
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&focusedCommentId=17829826#comment-17829826
]
Bruno Cadonna commented on KAFKA-16403:
---
I would think so since we have never enco
[
https://issues.apache.org/jira/browse/KAFKA-16403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17829824#comment-17829824
]
Bruno Cadonna commented on KAFKA-16403:
---
Thanks for the report [~soarez]!
Can you
[
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 c
[
https://issues.apache.org/jira/browse/KAFKA-16350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17825278#comment-17825278
]
Bruno Cadonna commented on KAFKA-16350:
---
Thanks for the report [~mjsax]!
I think
[
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 sep
[
https://issues.apache.org/jira/browse/KAFKA-16290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17822250#comment-17822250
]
Bruno Cadonna commented on KAFKA-16290:
---
I changed the version to 4.0.0.
> Invest
[
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 subscriptio
[
https://issues.apache.org/jira/browse/KAFKA-9062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17821066#comment-17821066
]
Bruno Cadonna commented on KAFKA-9062:
--
Closed it.
If we will run again into a simil
[
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
threa
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&focusedCommentId=17807174#comment-17807174
]
Bruno Cadonna commented on KAFKA-16139:
---
Note that since
https://github.com/apach
[
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&focusedCommentId=17805126#comment-17805126
]
Bruno Cadonna commented on KAFKA-9545:
--
[~ashwinpankaj] Thank you for verifying the
[
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 assign
[
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 testGroupId
[
https://issues.apache.org/jira/browse/KAFKA-15991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799019#comment-17799019
]
Bruno Cadonna commented on KAFKA-15991:
---
This is resolved via https://github.com/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
{{TaskCorrup
[
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
{{TaskCorrup
[
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 res
[
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
{{TaskCorrup
[
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 {{TaskCorrupt
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: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-14454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17796101#comment-17796101
]
Bruno Cadonna commented on KAFKA-14454:
---
[~sagarrao] First of all my apologies! I
[
https://issues.apache.org/jira/browse/KAFKA-14454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17796079#comment-17796079
]
Bruno Cadonna commented on KAFKA-14454:
---
[~sagarrao] Was the error:
{code:java}
j
[
https://issues.apache.org/jira/browse/KAFKA-9545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17796053#comment-17796053
]
Bruno Cadonna commented on KAFKA-9545:
--
I am reopening this issue, because
https://g
[
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&focusedCommentId=17795221#comment-17795221
]
Bruno Cadonna commented on KAFKA-15991:
---
Thanks for the ticket [~lianetm]!
I have
[
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 e
[
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 group.id
1 - 100 of 1008 matches
Mail list logo
