Haruki Okada created KAFKA-16541:
Summary: Potential leader epoch checkpoint file corruption on OS
crash
Key: KAFKA-16541
URL: https://issues.apache.org/jira/browse/KAFKA-16541
Project: Kafka
Calvin Liu created KAFKA-16540:
--
Summary: Update partitions when the min isr config is updated.
Key: KAFKA-16540
URL: https://issues.apache.org/jira/browse/KAFKA-16540
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-15586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Calvin Liu resolved KAFKA-15586.
Resolution: Fixed
> Clean shutdown detection, server side
> -
David Arthur created KAFKA-16539:
Summary: Can't update specific broker configs in pre-migration mode
Key: KAFKA-16539
URL: https://issues.apache.org/jira/browse/KAFKA-16539
Project: Kafka
José Armando García Sancio created KAFKA-16538:
--
Summary: UpdateFeatures for kraft.version
Key: KAFKA-16538
URL: https://issues.apache.org/jira/browse/KAFKA-16538
Project: Kafka
José Armando García Sancio created KAFKA-16537:
--
Summary: RemoveVoter RPC and request handling
Key: KAFKA-16537
URL: https://issues.apache.org/jira/browse/KAFKA-16537
Project: Kafka
José Armando García Sancio created KAFKA-16536:
--
Summary: Use BeginQuorumEpoch as the leader's heartbeat
Key: KAFKA-16536
URL: https://issues.apache.org/jira/browse/KAFKA-16536
Project:
José Armando García Sancio created KAFKA-16535:
--
Summary: AddVoter RPC and request handling
Key: KAFKA-16535
URL: https://issues.apache.org/jira/browse/KAFKA-16535
Project: Kafka
José Armando García Sancio created KAFKA-16534:
--
Summary: Sending UpdateVoter request and response handling
Key: KAFKA-16534
URL: https://issues.apache.org/jira/browse/KAFKA-16534
José Armando García Sancio created KAFKA-16533:
--
Summary: UpdateVoter RPC and request handling
Key: KAFKA-16533
URL: https://issues.apache.org/jira/browse/KAFKA-16533
Project: Kafka
José Armando García Sancio created KAFKA-16532:
--
Summary: Support for first leader bootstrapping the voter set
Key: KAFKA-16532
URL: https://issues.apache.org/jira/browse/KAFKA-16532
José Armando García Sancio created KAFKA-16531:
--
Summary: Fix check-quorum calculation to no assume that the leader
is in the voter set
Key: KAFKA-16531
URL:
José Armando García Sancio created KAFKA-16530:
--
Summary: Fix high-watermark calculation to no assume the leader is
in the voter set
Key: KAFKA-16530
URL:
José Armando García Sancio created KAFKA-16529:
--
Summary: Response handling and request sending for voters RPCs
Key: KAFKA-16529
URL: https://issues.apache.org/jira/browse/KAFKA-16529
Lianet Magrans created KAFKA-16528:
--
Summary: Reset member heartbeat interval when request sent
Key: KAFKA-16528
URL: https://issues.apache.org/jira/browse/KAFKA-16528
Project: Kafka
Issue
José Armando García Sancio created KAFKA-16527:
--
Summary: RPC changes and request handling
Key: KAFKA-16527
URL: https://issues.apache.org/jira/browse/KAFKA-16527
Project: Kafka
Updated. :)
Thanks for the reviews
Justine
On Thu, Apr 11, 2024 at 11:01 AM Jun Rao wrote:
> Hi, Justine,
>
> Thanks for the updated KIP.
>
> Perhaps it's better to name the new config unstable.feature.versions.enable
> since there could be multiple unstable versions.
>
> Other than that, the
Hi everyone,
I have made some changes to take in account comments. I have replaced the
ConsumerRecord by Record. As it was not allowed by checkstyle, I have
modified its configuration. I hope that's ok.
I find this new version better. Thanks for your help.
Regards,
Fred
José Armando García Sancio created KAFKA-16526:
--
Summary: Change to quorum state for KIP-853
Key: KAFKA-16526
URL: https://issues.apache.org/jira/browse/KAFKA-16526
Project: Kafka
Hi, Justine,
Thanks for the updated KIP.
Perhaps it's better to name the new config unstable.feature.versions.enable
since there could be multiple unstable versions.
Other than that, the KIP looks good to me.
Jun
On Thu, Apr 11, 2024 at 9:06 AM Justine Olshan
wrote:
> The original config
José Armando García Sancio created KAFKA-16525:
--
Summary: Request manager and raft channel discover node endpoints
Key: KAFKA-16525
URL: https://issues.apache.org/jira/browse/KAFKA-16525
José Armando García Sancio created KAFKA-16524:
--
Summary: Metrics for KIP-853
Key: KAFKA-16524
URL: https://issues.apache.org/jira/browse/KAFKA-16524
Project: Kafka
Issue Type:
> Is making it optional a good solution? Or should we recover the snapshot
if not found before uploading it?
IMO, we should recover the snapshot if it is not found.
> But what if the topic is created before v2.8.0 and old log segments are
deleted, how could we recover all the producer snapshot
José Armando García Sancio created KAFKA-16523:
--
Summary: kafka-metadata-quorum add voter and remove voter changes
Key: KAFKA-16523
URL: https://issues.apache.org/jira/browse/KAFKA-16523
José Armando García Sancio created KAFKA-16522:
--
Summary: Implement Admin client changes for adding and removing
votes
Key: KAFKA-16522
URL: https://issues.apache.org/jira/browse/KAFKA-16522
José Armando García Sancio created KAFKA-16521:
--
Summary: Implement kafka-metadata-quorum describe changes for
KIP-853
Key: KAFKA-16521
URL: https://issues.apache.org/jira/browse/KAFKA-16521
José Armando García Sancio created KAFKA-16520:
--
Summary: Implement changes to DescribeQuorum response
Key: KAFKA-16520
URL: https://issues.apache.org/jira/browse/KAFKA-16520
Project:
José Armando García Sancio created KAFKA-16519:
--
Summary: Expose the supported and finalized kraft.version in
ApiVersions response
Key: KAFKA-16519
URL:
José Armando García Sancio created KAFKA-16518:
--
Summary: Implement storage tool changes for KIP-853
Key: KAFKA-16518
URL: https://issues.apache.org/jira/browse/KAFKA-16518
Project: Kafka
José Armando García Sancio created KAFKA-16517:
--
Summary: Do not decode metadata records in the internal kraft
partition listener
Key: KAFKA-16517
URL:
José Armando García Sancio created KAFKA-16516:
--
Summary: Fix the controller node provider for broker to control
channel
Key: KAFKA-16516
URL: https://issues.apache.org/jira/browse/KAFKA-16516
José Armando García Sancio created KAFKA-16515:
--
Summary: Fix the ZK Metadata cache use of voter static
configuration
Key: KAFKA-16515
URL: https://issues.apache.org/jira/browse/KAFKA-16515
Sal Sorrentino created KAFKA-16514:
--
Summary: Kafka Streams: stream.close(CloseOptions) does not
respect options.leaveGroup flag.
Key: KAFKA-16514
URL: https://issues.apache.org/jira/browse/KAFKA-16514
omkreddy merged PR #597:
URL: https://github.com/apache/kafka-site/pull/597
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
VedarthConfluent opened a new pull request, #597:
URL: https://github.com/apache/kafka-site/pull/597
This change should fix the broken video on quickstart page
https://kafka.apache.org/quickstart.
Currently observing following error:-
`quickstart:297 Refused to frame
The original config was never actually approved in any KIP. But we can say
it is deprecated.
I can change the config name.
Justine
On Thu, Apr 11, 2024 at 8:52 AM Jun Rao wrote:
> Hi, Justine,
>
> Thanks for the updated KIP.
>
> Would unstable.feature.version.enable be a clearer name? Also,
Hi All,
When tackling the issue outlined in
https://issues.apache.org/jira/browse/KAFKA-16088, which pertains to
transitioning from RemoteLogSegment to LocalLogSegment during log
compaction in a fetch request, I'm seeking some suggestions or guidance
from the community to advance
*Current
Hi everyone,
I would like to start a discussion for
KIP-1037: Allow WriteTxnMarkers API with Alter Cluster Permission
https://cwiki.apache.org/confluence/display/KAFKA/KIP-1037%3A+Allow+WriteTxnMarkers+API+with+Alter+Cluster+Permission
The WriteTxnMarkers API was originally used for
Hi, Justine,
Thanks for the updated KIP.
Would unstable.feature.version.enable be a clearer name? Also, should we
remove/deprecate unstable.metadata.versions.enable in this KIP?
Jun
On Tue, Apr 9, 2024 at 9:09 AM Justine Olshan
wrote:
> Hi Jun,
>
> Makes sense to me. It seems like KIP-1014
Nikhil Ramakrishnan created KAFKA-16513:
---
Summary: Allow WriteTxnMarkers API with Alter Cluster Permission
Key: KAFKA-16513
URL: https://issues.apache.org/jira/browse/KAFKA-16513
Project: Kafka
Tobias Liefke created KAFKA-16512:
-
Summary: Top level menu on Kafka homepage not working
Key: KAFKA-16512
URL: https://issues.apache.org/jira/browse/KAFKA-16512
Project: Kafka
Issue Type:
Hi Mickael!
Any thoughts on this?
Thanks!
On Wed, 3 Apr 2024 at 13:21, Elxan Eminov wrote:
> Hi Mickael,
> Thanks for your response and apologies for a huge delay in mine.
>
> My thinking is that any partition could go stale if there are no records
> being produced into it. If enough of such
Francois Visconte created KAFKA-16511:
-
Summary: Leaking tiered segments
Key: KAFKA-16511
URL: https://issues.apache.org/jira/browse/KAFKA-16511
Project: Kafka
Issue Type: Bug
Hi Matthias, Bruno,
1.a During my previous comment, by Processor Node ID, I meant
Processor name. This is important information to expose in the handler
as it allows users to identify the location of the exception in the
topology.
I assume this information could be useful in other places, that's
BR,
Michał Łowicki
On Fri, 5 Apr 2024 at 15:59, David Jacot
wrote:
> Thanks, Michal. Let me add it to my review queue.
Gentle ping ;-)
>
> BR,
> David
>
> On Fri, Apr 5, 2024 at 3:29 PM Michał Łowicki wrote:
>
> > Hi there!
> >
> > Created
[
https://issues.apache.org/jira/browse/KAFKA-15610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved KAFKA-15610.
Fix Version/s: 3.8.0
Resolution: Fixed
> Fix `CoreUtils.swallow()` test gaps
>
[
https://issues.apache.org/jira/browse/KAFKA-16482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved KAFKA-16482.
Fix Version/s: 3.8.0
Resolution: Fixed
> Eliminate the IDE warnings of accepting
Hi Matthias,
1.a
With processor node ID, I mean the ID that is exposed in the tags of
processor node metrics. That ID cannot be internal since it is exposed
in metrics. I think the processor name and the processor node ID is the
same thing. I followed how the processor node ID is set in
Hi Kirk,
I have made the test and I confirm that checkstyle is complaining
(Disallowed import - org.apache.kafka.common.record.Record.) if I use
Record class in the RecordDeserialisationException.
An alternative might be to add key(), value(), headers() etc methods
directly in the exception.
Hi Ivan,
I agree with Andrew that we can save cluster ID checking for later. This
feature is opt-in and if necessary we can add a note to users about only
enabling it if they can be certain that the same cluster will always be
resolved by the bootstrap servers. This would apply regardless of
Hi Colin,
Thanks for the KIP!
I'm sorry for reopening this old discussion thread but I don't know where
else I can ask my question.
I wanted to use the newly updated kafka-configs.sh tool to dynamically
update the ssl keystore in the controller node, but I still couldn't
figure it out.
Is it
Thanks for your feedback.
Kirk, that's a good point. I will check if there are other ways of raising
an exception than the deserialisation itself.
About Record, I agree I think it would be a better choice and my initial
version was using it. But then I realised that this class might not be
52 matches
Mail list logo
