Re: [DISCUSS] KIP-937 Improve Message Timestamp Validation

Hi all, Please ignore this message. I'm just using this message to bump this thread so that it will show up in Gaurav's inbox. He wanted to send out review comments for this KIP. Cheers, Kowshik On Wed, Jun 7, 2023 at 1:39 PM Beyene, Mehari wrote: > > Although it's more verbose, splitting

Re: [ANNOUNCE] New PMC chair: Mickael Maison

Thanks a lot Jun for your hard work and contributions over the years. Congrats Mickael on your new role, well deserved! Wishing both of you, and the rest of the community the very best! Cheers, Kowshik On Sat, Apr 22, 2023, 6:38 PM Satish Duggana wrote: > Thanks a lot Jun for your

Re: [ANNOUNCE] New Kafka PMC Member: Chris Egerton

Congrats Chris! On Thu, Mar 9, 2023 at 1:33 PM Divij Vaidya wrote: > Congratulations Chris! I am in awe with the amount of effort you put in > code reviews and helping out the community members. Very well deserved. > > -- > Divij Vaidya > > > > On Thu, Mar 9, 2023 at 9:49 PM Jorge Esteban

Re: [ANNOUNCE] New Kafka PMC Member: David Arthur

Congrats David! On Thu, Mar 9, 2023 at 12:09 PM Lucas Brutschy wrote: > Congratulations! > > On Thu, Mar 9, 2023 at 8:37 PM Manikumar > wrote: > > > > Congrats David! > > > > > > On Fri, Mar 10, 2023 at 12:24 AM Josep Prat > > > wrote: > > > > > > Congrats David! > > > > > > ——— > > > Josep

Re: [ANNOUNCE] New committer: Lucas Bradstreet

Congratulations, Lucas! Cheers, Kowshik On Thu, Feb 16, 2023, 2:07 PM Justine Olshan wrote: > Congratulations Lucas! > > Thanks for your mentorship on some of my KIPs as well :) > > On Thu, Feb 16, 2023 at 1:56 PM Jun Rao wrote: > > > Hi, Everyone, > > > > The PMC of Apache Kafka is pleased

Re: [ANNOUNCE] New committer: Edoardo Comar

Congrats, Eduardo! Cheers, Kowshik On Tue, Jan 17, 2023, 4:54 PM Guozhang Wang wrote: > Congratulations, Edoardo! > > On Tue, Jan 10, 2023 at 9:11 AM Bruno Cadonna wrote: > > > Congrats! > > > > Best, > > Bruno > > > > On 10.01.23 11:00, Edoardo Comar wrote: > > > Many thanks everyone ! > >

Re: [ANNOUNCE] New committer: Josep Prat

Congrats, Josep! Cheers, Kowshik On Tue, Jan 17, 2023, 4:57 PM Guozhang Wang wrote: > Congratulations, Josep! > > On Tue, Jan 3, 2023 at 11:23 AM Josep Prat > wrote: > > > Thanks all again! :) > > > > On Tue, Jan 3, 2023 at 6:19 PM Bill Bejeck > > wrote: > > > > > Congratulations, Josep! >

Re: [ANNOUNCE] New committer: Satish Duggana

Congrats, Satish! Cheers, Kowshik On Tue, Jan 17, 2023, 5:17 PM John Roesler wrote: > Ay, sorry about my autocorrect, Satish. > > On Tue, Jan 17, 2023, at 19:13, John Roesler wrote: > > Congratulations, Salish! I missed the announcement before. > > > > -John > > > > On Tue, Jan 17, 2023, at

Re: [ANNOUNCE] New committer: Justine Olshan

Congrats, Justine! Cheers, Kowshik On Tue, Jan 17, 2023, 4:53 PM Guozhang Wang wrote: > Congratulations, Justine (I'm also late)! > > On Wed, Jan 11, 2023 at 12:17 AM Bruno Cadonna wrote: > > > Hi Justine, > > > > Re-reading my message I realized that my message might be > > misinterpreted.

Re: [ANNOUNCE] New committer: Stanislav Kozlovski

Congratulations Stan! Cheers, Kowshik On Tue, Jan 17, 2023, 5:11 PM John Roesler wrote: > Congrats, Stanislav! > -John > > On Tue, Jan 17, 2023, at 18:56, Ismael Juma wrote: > > Congratulations Stanislav! > > > > Ismael > > > > On Tue, Jan 17, 2023 at 7:51 AM Jun Rao > wrote: > > > >> Hi,

[jira] [Created] (KAFKA-13701) Pin background worker threads for certain background work (ex: UnifiedLog.flush())

Kowshik Prakasam created KAFKA-13701: Summary: Pin background worker threads for certain background work (ex: UnifiedLog.flush()) Key: KAFKA-13701 URL: https://issues.apache.org/jira/browse/KAFKA-13701

Re: [ANNOUNCE] New Kafka PMC member: David Jacot

Congrats David! Very well deserved. Cheers, Kowshik On Fri, Dec 17, 2021 at 9:06 PM Kirk True wrote: > Congrats! > > On Fri, Dec 17, 2021, at 8:55 PM, Luke Chen wrote: > > Congrats, David! > > Well deserved. > > > > Luke > > > > deng ziming 於 2021年12月18日 週六 上午7:47 寫道： > > > > > Congrats

Re: [VOTE] KIP-778 KRaft upgrades

Hi David, Excellent work. Looking forward to this KIP. +1 (non-binding). Cheers, Kowshik On Wed, Dec 15, 2021 at 10:40 AM David Arthur wrote: > Hey all, I realized I omitted a small change to the public APIs regarding > finalized feature versions. I've updated the KIP with these changes.

Re: [DISCUSS] KIP-778 KRaft Upgrades

Hi David, Thanks for the explanations. Few comments below. 7001. Sounds good. 7002. Sounds good. The --force-downgrade-all option can be used for the basic CLI while the --force-downgrade option can be used for the advanced CLI. 7003. I like your suggestion on separate sub-commands, I agree

Re: [DISCUSS] KIP-778 KRaft Upgrades

Hi David, Thanks for the great KIP! It's good to see KIP-584 is starting to get used. Few comments below. 7001. In the UpdateFeaturesRequest definition, there is a newly introduced ForceDowngrade parameter. There is also an existing AllowDowngrade parameter. My understanding is that the

[jira] [Created] (KAFKA-13070) LogManager shutdown races with periodic work scheduled by the instance

Kowshik Prakasam created KAFKA-13070: Summary: LogManager shutdown races with periodic work scheduled by the instance Key: KAFKA-13070 URL: https://issues.apache.org/jira/browse/KAFKA-13070

[jira] [Created] (KAFKA-13068) Rename Log to UnifiedLog

Kowshik Prakasam created KAFKA-13068: Summary: Rename Log to UnifiedLog Key: KAFKA-13068 URL: https://issues.apache.org/jira/browse/KAFKA-13068 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-12977) Eliminate temporary ProducerStateManager in Log recovery logic

Kowshik Prakasam created KAFKA-12977: Summary: Eliminate temporary ProducerStateManager in Log recovery logic Key: KAFKA-12977 URL: https://issues.apache.org/jira/browse/KAFKA-12977 Project

[jira] [Created] (KAFKA-12955) Fix LogLoader to pass materialized list of segments for deletion

Kowshik Prakasam created KAFKA-12955: Summary: Fix LogLoader to pass materialized list of segments for deletion Key: KAFKA-12955 URL: https://issues.apache.org/jira/browse/KAFKA-12955 Project

[jira] [Created] (KAFKA-12923) Log.splitOverflowedSegment logic can skip producer state snapshot deletion

Kowshik Prakasam created KAFKA-12923: Summary: Log.splitOverflowedSegment logic can skip producer state snapshot deletion Key: KAFKA-12923 URL: https://issues.apache.org/jira/browse/KAFKA-12923

[jira] [Created] (KAFKA-12876) Log.roll() could forever delete producer state snapshot of empty active segment

Kowshik Prakasam created KAFKA-12876: Summary: Log.roll() could forever delete producer state snapshot of empty active segment Key: KAFKA-12876 URL: https://issues.apache.org/jira/browse/KAFKA-12876

[jira] [Created] (KAFKA-12875) Change Log layer segment map mutations to avoid absence of active segment

Kowshik Prakasam created KAFKA-12875: Summary: Change Log layer segment map mutations to avoid absence of active segment Key: KAFKA-12875 URL: https://issues.apache.org/jira/browse/KAFKA-12875

[jira] [Created] (KAFKA-12867) Trogdor ConsumeBenchWorker quits prematurely with maxMessages config

Kowshik Prakasam created KAFKA-12867: Summary: Trogdor ConsumeBenchWorker quits prematurely with maxMessages config Key: KAFKA-12867 URL: https://issues.apache.org/jira/browse/KAFKA-12867 Project

[jira] [Created] (KAFKA-12722) Evaluate moving replaceSegments into LogSegments class

Kowshik Prakasam created KAFKA-12722: Summary: Evaluate moving replaceSegments into LogSegments class Key: KAFKA-12722 URL: https://issues.apache.org/jira/browse/KAFKA-12722 Project: Kafka

Re: [ANNOUNCE] New Kafka PMC Member: Bill Bejeck

Congrats Bill! Cheers, Kowshik On Mon, Apr 12, 2021, 11:15 AM Randall Hauch wrote: > Congratulations, Bill! > > On Mon, Apr 12, 2021 at 11:02 AM Guozhang Wang wrote: > > > Congratulations Bill ! > > > > Guozhang > > > > On Wed, Apr 7, 2021 at 6:16 PM Matthias J. Sax wrote: > > > > > Hi, > >

Re: [ANNOUNCE] New Kafka PMC Member: Randall Hauch

Congrats Randall! Cheers, Kowshik On Sat, Apr 17, 2021, 5:28 AM Rankesh Kumar wrote: > Congratulations, Randall! > Best regards, > Rankesh Kumar > Partner Solutions Engineer > +91 (701)913-0147 > Follow us: Blog • Slack • Twitter • YouTube > > > On 17-Apr-2021, at 1:41 PM, Tom Bentley

[jira] [Created] (KAFKA-12575) Eliminate Log.isLogDirOffline boolean attribute

Kowshik Prakasam created KAFKA-12575: Summary: Eliminate Log.isLogDirOffline boolean attribute Key: KAFKA-12575 URL: https://issues.apache.org/jira/browse/KAFKA-12575 Project: Kafka

[jira] [Created] (KAFKA-12571) Eliminate LogEndOffset dependency on LeaderEpochFileCache c'tor

Kowshik Prakasam created KAFKA-12571: Summary: Eliminate LogEndOffset dependency on LeaderEpochFileCache c'tor Key: KAFKA-12571 URL: https://issues.apache.org/jira/browse/KAFKA-12571 Project

[jira] [Created] (KAFKA-12551) Refactor Kafka Log layer

Kowshik Prakasam created KAFKA-12551: Summary: Refactor Kafka Log layer Key: KAFKA-12551 URL: https://issues.apache.org/jira/browse/KAFKA-12551 Project: Kafka Issue Type: Improvement

[jira] [Created] (KAFKA-12552) Extract segments map out of Log class into separate class

Kowshik Prakasam created KAFKA-12552: Summary: Extract segments map out of Log class into separate class Key: KAFKA-12552 URL: https://issues.apache.org/jira/browse/KAFKA-12552 Project: Kafka

[jira] [Created] (KAFKA-12554) Split Log layer into UnifiedLog and LocalLog

Kowshik Prakasam created KAFKA-12554: Summary: Split Log layer into UnifiedLog and LocalLog Key: KAFKA-12554 URL: https://issues.apache.org/jira/browse/KAFKA-12554 Project: Kafka Issue

[jira] [Created] (KAFKA-12553) Refactor Log layer recovery logic

Kowshik Prakasam created KAFKA-12553: Summary: Refactor Log layer recovery logic Key: KAFKA-12553 URL: https://issues.apache.org/jira/browse/KAFKA-12553 Project: Kafka Issue Type: Sub

Re: [ANNOUNCE] New Kafka PMC Member: Chia-Ping Tsai

Congrats Chia-Ping! On Tue, Mar 16, 2021, 6:16 PM Dongjin Lee wrote: > > > Best, > Dongjin > > On Tue, Mar 16, 2021 at 2:20 PM Konstantine Karantasis > wrote: > > > Congratulations Chia-Ping! > > > > Konstantine > > > > On Mon, Mar 15, 2021 at 4:31 AM Rajini Sivaram > > wrote: > > > > >

Re: [VOTE] KIP - 405: Kafka Tiered Storage.

+1 (non-binding). Thanks for the excellent KIP! Cheers, Kowshik On Mon, Feb 15, 2021 at 2:50 AM Manikumar wrote: > Hi Satish, > > Thanks for driving this KIP. I’m sure there will be a few tweaks as we > implement the KIP, but I > think KIP is in good shape. > > I'm +1 (binding). > >

[jira] [Created] (KAFKA-12240) Proposal for Log layer refactoring

Kowshik Prakasam created KAFKA-12240: Summary: Proposal for Log layer refactoring Key: KAFKA-12240 URL: https://issues.apache.org/jira/browse/KAFKA-12240 Project: Kafka Issue Type

Re: [ANNOUNCE] Apache Kafka 2.7.0

umar, Anna Povzner, Antony > Stubbs, > > > Arjun Satish, Ashish Roy, Auston, Badai Aqrandista, Benoit Maggi, bill, > > > Bill Bejeck, Bob Barrett, Boyang Chen, Brian Byrne, Bruno Cadonna, Can > > > Cecen, Cheng Tan, Chia-Ping Tsai, Chris Egerton, Colin Patrick McCabe, &

Re: [VOTE] 2.7.0 RC5

Hi Bill, Just a heads up that KAFKA-9393 that was previously marked as fixed in 2.7.0 has now been changed to 2.8.0. The corresponding PR is not present in 2.7.0 commit history. Please could you regenerate the release notes to help pick up this change? Cheers, Kowshik On Tue, Dec 15, 2020 at

Re: [DISCUSS] KIP-405: Kafka Tiered Storage

m remote storage to [LSO, ELO]." I > mentioned > > > an > > > > > issue > > > > > > > earlier. Suppose the leader's local start offset is 100. The > > > follower > > > > > finds > > > > > > > a remote segment

[jira] [Created] (KAFKA-10832) Recovery logic is using incorrect ProducerStateManager instance when updating producers

Kowshik Prakasam created KAFKA-10832: Summary: Recovery logic is using incorrect ProducerStateManager instance when updating producers Key: KAFKA-10832 URL: https://issues.apache.org/jira/browse/KAFKA-10832

Re: Unable to sign into VPN

Sorry! On Tue, Dec 1, 2020 at 3:19 PM Kowshik Prakasam wrote: > Please ignore this email, it was sent to the wrong email address. > > On Tue, Dec 1, 2020 at 3:19 PM Kowshik Prakasam > wrote: > >> Hi, >> >> I'm unable to sign into VPN. When I goto Okta and click

Re: Unable to sign into VPN

Please ignore this email, it was sent to the wrong email address. On Tue, Dec 1, 2020 at 3:19 PM Kowshik Prakasam wrote: > Hi, > > I'm unable to sign into VPN. When I goto Okta and click on "Pulse Secure > VPN", I keep getting the attached error message. Could you

Unable to sign into VPN

Hi, I'm unable to sign into VPN. When I goto Okta and click on "Pulse Secure VPN", I keep getting the attached error message. Could you please help resolve this? Thanks, Kowshik

Re: [DISCUSS] KIP-405: Kafka Tiered Storage

+Storage#KIP405:KafkaTieredStorage-MeetingNotes Cheers, Kowshik On Tue, Nov 10, 2020 at 11:39 PM Kowshik Prakasam wrote: > Hi Harsha, > > The goal we discussed is to aim for preview in AK 3.0. In order to get us > there, it will be useful to think about the order in which the

Looking for a PR review for FinalizedFeatureCache cleanup

Hi, I'm looking for a PR review for a small cleanup/refactor to use string interpolation in FinalizedFeatureCache class. Please could one of you help review this change? Here is a link to the PR: https://github.com/apache/kafka/pull/9602 Cheers, Kowshik

Re: KAFKA-10723: LogManager thread pool activity post shutdown

In case you are interested in the fix, I've uploaded a PR: https://github.com/apache/kafka/pull/9596 containing fix #2 mentioned in the jira description. Cheers, Kowshik On Sat, Nov 14, 2020 at 12:40 PM Kowshik Prakasam wrote: > Hey everyone, > > When I was seeing Broker error logs

KAFKA-10723: LogManager thread pool activity post shutdown

Hey everyone, When I was seeing Broker error logs, I noted that the LogManager leaks internal thread pool activity during KafkaServer shutdown sequence, whenever it encounters an internal error. I have explained the issue in this jira: https://issues.apache.org/jira/browse/KAFKA-10723 , and have

[jira] [Created] (KAFKA-10723) LogManager shutdown error handler doesn't shutdown all internal thread pools

Kowshik Prakasam created KAFKA-10723: Summary: LogManager shutdown error handler doesn't shutdown all internal thread pools Key: KAFKA-10723 URL: https://issues.apache.org/jira/browse/KAFKA-10723

Re: [DISCUSS] KIP-405: Kafka Tiered Storage

ng with unit tests, systems > tests will be delivered and we can call that as preview. We will be > running this in our production and continue to provide the data and metrics > to push this feature to GA. > > > > On Tue, Nov 10, 2020 at 10:07 AM, Kowshik Prakasam

Re: [DISCUSS] KIP-405: Kafka Tiered Storage

in when a broker is restarted." Could you describe the format > > and the location of the file? Also, could the same message be processed > by > > RLMM again after broker restart? If so, how do we handle that? > > > > 5114. Message format > > 5114.1 There are two

Re: [DISCUSS] KIP-405: Kafka Tiered Storage

g local log segments and metadata. Additionally, a > wrapper class can be provided (implementing the higher level Log interface) > which will contain any/all logic surrounding tiered data. The wrapper > class will wrap around an instance of the Log class delegating the local > log log

Looking for PR review for small doc update

Hi all, I'm looking for a PR review for a small doc update in FinalizedFeatureChangeListener. Would you be able to please help review it? Link to PR: https://github.com/apache/kafka/pull/9562 . Cheers, Kowshik

KAFKA-10624: Looking for PR review

Hi all, I'm looking for a PR review for a small PR to address KAFKA-10624 : https://github.com/apache/kafka/pull/9561. Would you be able to please help review it? Cheers, Kowshik

Re: [VOTE] KIP-584: Versioning scheme for features

t 13, 2020 at 4:50 PM Kowshik Prakasam > wrote: > > > Hi all, > > > > I wanted to let you know that I have made the following minor changes to > > the `kafka-features` CLI tool description in the KIP-584 write up. The > > purpose is to ensure the design is correct

Re: [DISCUSS] KIP-405: Kafka Tiered Storage

o > > > > >> have to include all other fields not changed. 609.3 Could you > document > > > > >> which process makes the following transitions DELETE_MARKED, > > > > >> DELETE_STARTED, DELETE_FINISHED? > > > > >> > > > > >> > > > > >> > > >

[jira] [Created] (KAFKA-10624) FeatureZNodeStatus should use sealed trait instead of Enumeration

Kowshik Prakasam created KAFKA-10624: Summary: FeatureZNodeStatus should use sealed trait instead of Enumeration Key: KAFKA-10624 URL: https://issues.apache.org/jira/browse/KAFKA-10624 Project

[jira] [Created] (KAFKA-10623) Refactor code to avoid discovery conflicts for classes:{Supported|Finalized}VersionRange

Kowshik Prakasam created KAFKA-10623: Summary: Refactor code to avoid discovery conflicts for classes:{Supported|Finalized}VersionRange Key: KAFKA-10623 URL: https://issues.apache.org/jira/browse/KAFKA-10623

[jira] [Created] (KAFKA-10622) Implement support for feature version deprecation

Kowshik Prakasam created KAFKA-10622: Summary: Implement support for feature version deprecation Key: KAFKA-10622 URL: https://issues.apache.org/jira/browse/KAFKA-10622 Project: Kafka

[jira] [Created] (KAFKA-10621) Implement advanced CLI tool for feature versioning system

Kowshik Prakasam created KAFKA-10621: Summary: Implement advanced CLI tool for feature versioning system Key: KAFKA-10621 URL: https://issues.apache.org/jira/browse/KAFKA-10621 Project: Kafka

Looking for PR review for small clean up in TopicCommand

Hi all, I'm looking for a PR review for a small clean up in TopicCommand class. Here is a link to the PR: https://github.com/apache/kafka/pull/9465. I'd appreciate the help if any of you could review/merge this PR. Cheers, Kowshik

Re: [ANNOUNCE] New committer: A. Sophie Blee-Goldman

Congrats Sophie! Cheers, Kowshik On Mon, Oct 19, 2020 at 10:31 AM Bill Bejeck wrote: > Congratulations Sophie! > > -Bill > > On Mon, Oct 19, 2020 at 12:49 PM Leah Thomas wrote: > > > Congrats Sophie! > > > > On Mon, Oct 19, 2020 at 11:41 AM Matthias J. Sax > wrote: > > > > > Hi all, > > >

Re: [ANNOUNCE] New committer: Chia-Ping Tsai

Congrats! Cheers, Kowshik On Mon, Oct 19, 2020 at 10:40 AM Bruno Cadonna wrote: > Congrats! > > Best, > Bruno > > On 19.10.20 19:39, Sophie Blee-Goldman wrote: > > Congrats! > > > > On Mon, Oct 19, 2020 at 10:32 AM Bill Bejeck wrote: > > > >> Congratulations Chia-Ping! > >> > >> -Bill > >>

Re: [ANNOUNCE] New committer: David Jacot

Congrats David! Cheers, Kowshik On Fri, Oct 16, 2020, 9:21 AM Mickael Maison wrote: > Congratulations David! > > On Fri, Oct 16, 2020 at 6:05 PM Bill Bejeck wrote: > > > > Congrats David! Well deserved. > > > > -Bill > > > > On Fri, Oct 16, 2020 at 12:01 PM Gwen Shapira wrote: > > > > > The

Re: [VOTE] KIP-584: Versioning scheme for features

Please let me know if you have any questions. Cheers, Kowshik On Thu, Oct 8, 2020 at 1:12 AM Kowshik Prakasam wrote: > Hi Jun, > > This is a very good point. I have updated the feature version deprecation > section mentioning the same: > https://cwiki.apache.org/confluence/display/K

[jira] [Created] (KAFKA-10599) Implement basic CLI tool for feature versioning system

Kowshik Prakasam created KAFKA-10599: Summary: Implement basic CLI tool for feature versioning system Key: KAFKA-10599 URL: https://issues.apache.org/jira/browse/KAFKA-10599 Project: Kafka

Re: [VOTE] KIP-584: Versioning scheme for features

e client > version metric) before deploying a release that deprecates it. > > Thanks, > > Jun > > On Tue, Oct 6, 2020 at 3:46 PM Kowshik Prakasam > wrote: > > > Hi Jun, > > > > I have added the following details in the KIP-584 write up: >

Re: [VOTE] KIP-584: Versioning scheme for features

ses the release version and this KIP > uses an integer for versions. How do we bridge the gap between the two? > Does min.version still make sense for IBP as a feature? > > Thanks, > > Jun > > On Fri, Sep 25, 2020 at 5:57 PM Kowshik Prakasam > wrote: > > > Hi Colin, &

Re: [DISCUSS] Apache Kafka 2.7.0 release

Hey Bill, For KIP-584 , we are in the process of reviewing/merging the write path PR into AK trunk: https://github.com/apache/kafka/pull/9001 . As far as the KIP goes, this PR is a major milestone. The PR merge will hopefully be done before EOD

Re: [VOTE] KIP-584: Versioning scheme for features

://github.com/apache/kafka/pull/9001. Cheers, Kowshik On Fri, Sep 25, 2020 at 4:57 PM Kowshik Prakasam wrote: > Hi Jun, > > Thanks for the feedback. It's a very good point. I have now modified the > KIP-584 write-up "goals" section a bit. It now mentions one of the goals as >

Re: [VOTE] KIP-584: Versioning scheme for features

t; On Tue, Sep 22, 2020, at 00:43, Kowshik Prakasam wrote: > > Hi all, > > > > I wanted to let you know that I have made the following changes to the > > KIP-584 write up. The purpose is to ensure the design is correct for a > few > > things which came up during implem

Re: [VOTE] KIP-584: Versioning scheme for features

of an incompatible broker because the broker will eventually shutdown automatically (when reacting to the incompatibility). Please let me know if you have any questions. Cheers, Kowshik On Mon, Jun 8, 2020 at 3:32 AM Kowshik Prakasam wrote: > Hi all, > > I wanted to let you know that I

Re: [DISCUSS] KIP-405: Kafka Tiered Storage

; >>>> > >>>> > >>>> > >>>> 5004. In the default implementation of RLMM (using the internal topic > >>>> __remote_log_metadata), a separate topic called > >>>> __remote_segments_to_be

Re: [DISCUSS] KIP-405: Kafka Tiered Storage

Hi Harsha/Satish, Thanks for the great KIP. Below are the first set of questions/suggestions I had after making a pass on the KIP. 5001. Under the section "Follower fetch protocol in detail", the next-local-offset is the offset upto which the segments are copied to remote storage. Instead, would

Re: [ANNOUNCE] New committer: Boyang Chen

Congrats, Boyang! :) Cheers, Kowshik On Tue, Jun 23, 2020 at 8:43 AM Aparnesh Gaurav wrote: > Congrats Boyang. > > On Tue, 23 Jun, 2020, 9:07 PM Vahid Hashemian, > wrote: > > > Congrats Boyang! > > > > --Vahid > > > > On Tue, Jun 23, 2020 at 6:41 AM Wang (Leonard) Ge > > wrote: > > > > >

[jira] [Resolved] (KAFKA-10157) Multiple tests failed due to "Failed to process feature ZK node change event"

[ https://issues.apache.org/jira/browse/KAFKA-10157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kowshik Prakasam resolved KAFKA-10157. -- Resolution: Fixed > Multiple tests failed due to "Failed to process feature

Re: [VOTE] KIP-584: Versioning scheme for features

: https://cwiki.apache.org/confluence/display/KAFKA/KIP-584%3A+Versioning+scheme+for+features#KIP584:Versioningschemeforfeatures-FeatureZKnodestatus . Please let me know if you have any questions or concerns. Cheers, Kowshik Cheers, Kowshik On Tue, Apr 28, 2020 at 11:24 PM Kowshik Prakasam wrote

Re: [DISCUSS] Apache Kafka 2.6.0 release

Hi Randall, We have to remove KIP-584 from the release plan, as this item will not be completed for 2.6 release (although KIP is accepted). We plan to include it in a next release. Cheers, Kowshik On Fri, May 29, 2020 at 11:43 AM Maulin Vasavada wrote: > Hi Randall Hauch > > Can we add

[jira] [Created] (KAFKA-10028) KIP-584: Implement write path for versioning scheme for features

Kowshik Prakasam created KAFKA-10028: Summary: KIP-584: Implement write path for versioning scheme for features Key: KAFKA-10028 URL: https://issues.apache.org/jira/browse/KAFKA-10028 Project

[jira] [Resolved] (KAFKA-10026) KIP-584: Implement read path for versioning scheme for features

[ https://issues.apache.org/jira/browse/KAFKA-10026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kowshik Prakasam resolved KAFKA-10026. -- Resolution: Duplicate Duplicate of KAFKA-10027 > KIP-584: Implement read p

[jira] [Created] (KAFKA-10027) KIP-584: Implement read path for versioning scheme for features

Kowshik Prakasam created KAFKA-10027: Summary: KIP-584: Implement read path for versioning scheme for features Key: KAFKA-10027 URL: https://issues.apache.org/jira/browse/KAFKA-10027 Project

[jira] [Created] (KAFKA-10026) KIP-584: Implement read path for versioning scheme for features

Kowshik Prakasam created KAFKA-10026: Summary: KIP-584: Implement read path for versioning scheme for features Key: KAFKA-10026 URL: https://issues.apache.org/jira/browse/KAFKA-10026 Project

Re: Help! Can't add reviewers for Github Kafka PR

> -John > > On Sun, May 17, 2020, at 04:11, Kowshik Prakasam wrote: > > Hi all, > > > > My intent is to create a PR for review in > https://github.com/apache/kafka . > > However I find that I'm unable to add reviewers to my PR. Does this need > > any speci

Help! Can't add reviewers for Github Kafka PR

Hi all, My intent is to create a PR for review in https://github.com/apache/kafka . However I find that I'm unable to add reviewers to my PR. Does this need any specific permissions? If so, please could someone grant me access or help me understand what I need to do to get permissions to add

Re: [VOTE] KIP-584: Versioning scheme for features

! Cheers, Kowshik On Mon, Apr 27, 2020 at 12:15 PM Colin McCabe wrote: > Thanks, Kowshik. +1 (binding) > > best, > Colin > > On Sat, Apr 25, 2020, at 13:20, Kowshik Prakasam wrote: > > Hi Colin, > > > > Thanks for the explanation! I agree with you, and

Re: [VOTE] KIP-584: Versioning scheme for features

Cheers, Kowshik On Fri, Apr 24, 2020 at 8:50 PM Colin McCabe wrote: > On Fri, Apr 24, 2020, at 00:01, Kowshik Prakasam wrote: > > (Kowshik): Great point! However for case #1, I'm not sure why we need to > > create a '/features' ZK node with disabled features. Instead, do you see &

Re: [VOTE] KIP-584: Versioning scheme for features

> best, > Colin > > > On Tue, Apr 21, 2020, at 13:01, Dhruvil Shah wrote: > > Thanks for the KIP! +1 (non-binding) > > > > On Tue, Apr 21, 2020 at 6:09 AM David Jacot wrote: > > > > > Great KIP, thanks! +1 (non-binding) > > > > > > On Fri, Apr 17,

[VOTE] KIP-584: Versioning scheme for features

Hi all, I'd like to start a vote for KIP-584. The link to the KIP can be found here: https://cwiki.apache.org/confluence/display/KAFKA/KIP-584%3A+Versioning+scheme+for+features . Thanks! Cheers, Kowshik

Re: [DISCUSS] KIP-594 Safely abort Producer transactions during application shutdown

Hi, It appears "KIP-594" is already taken. Please see this existing link: https://cwiki.apache.org/confluence/display/KAFKA/KIP-594%3A+Expose+output+topic+names+from+TopologyTestDriver . To avoid a duplicate, please change your KIP number to pick the next available KIP number, as mentioned here:

Re: [DISCUSS] KIP-584: Versioning scheme for features

is still the text "*from* > {"max_version_level": > X} *to* {"max_version_level": X’}". It seems that it should say "from X to > Y"? > > 110. Could we add that we need to document the bumped version of each > feature in the u

Re: [DISCUSS] KIP-584: Versioning scheme for features

lay/KAFKA/KIP-584%3A+Versioning+scheme+for+features#KIP-584:Versioningschemeforfeatures-Whentouseversionedfeatureflags?> Cheers, Kowshik On Wed, Apr 15, 2020 at 6:24 PM Kowshik Prakasam wrote: > > Hi Jun, > > Thanks for the feedback! I have addressed the comments in the KIP. >

Re: [DISCUSS] KIP-584: Versioning scheme for features

Hi all, Thank you very much for all the insightful feedback! How do you feel about the KIP? Does the scope and the write up look OK to you, and is it time to call a vote? Cheers, Kowshik On Wed, Apr 15, 2020 at 1:08 PM Kowshik Prakasam wrote: > Hi Jun, > > Thank you for the sugg

Re: [DISCUSS] KIP-584: Versioning scheme for features

ge of the allowDowngrade field. In the validation section, we have > " > /features' from {"max_version_level": X} to {"max_version_level": X’}", it > seems that we need to mention Y there. > > Thanks, > > Jun > > On Wed, Apr 15, 2020 at

Re: [DISCUSS] KIP-584: Versioning scheme for features

t; over time? > > Jun > > > On Tue, Apr 14, 2020 at 6:49 PM Kowshik Prakasam > wrote: > > > Hi Jun, > > > > Thanks a lot for the feedback and the questions! > > Please find my response below. > > > > > 200. The UpdateFeaturesReque

Re: [DISCUSS] KIP-584: Versioning scheme for features

, "versions": "0+", > "about": "The error code, or 0 if there was no error." }, > { "name": "ErrorMessage", "type": "string", "versions": "0+", > "about":

Re: [DISCUSS] KIP-584: Versioning scheme for features

> broker to release version 2.6" than just "upgrade the broker to feature > version 7". > > 111. Sounds good. > > 120. When should a developer bump up the version of a feature? > > Jun > > On Tue, Apr 7, 2020 at 12:26 AM Kowshik Prakasam > wrote: > >

Re: [DISCUSS] KIP-584: Versioning scheme for features

use perspective, ideally, we shouldn't > require a > > new user to have an extra step such as running a bootstrap script unless > > it's truly necessary. If someone has a special need (all the cases you > > mentioned seem special cases?), they can configure a mode such

Re: [DISCUSS] KIP-584: Versioning scheme for features

> it's truly necessary. If someone has a special need (all the cases you > mentioned seem special cases?), they can configure a mode such that > features are enabled/disabled manually. > > Jun > > On Fri, Apr 3, 2020 at 5:54 PM Kowshik Prakasam > wrote: > > > Hi Jun

Re: [DISCUSS] KIP-584: Versioning scheme for features

rspective, ideally, we shouldn't > require a > > new user to have an extra step such as running a bootstrap script unless > > it's truly necessary. If someone has a special need (all the cases you > > mentioned seem special cases?), they can configure a mode such that > > featur

Re: [DISCUSS] KIP-584: Versioning scheme for features

minVersion/maxVersion for features use int64. Currently, our > > > release version schema is major.minor.bugfix (e.g. 2.5.0). It's > possible > > > for new features to be included in minor releases too. Should we make > the > > > feature versioning match the rel

Re: [DISCUSS] KIP-584: Versioning scheme for features

s also probably no reason to have these classes inherit from > each > > > other or have complex type relationships. One more nitpick is that > Kafka > > > generally doesn't use "get" in the function names of accessors. > > > > (Kowshik): Done, I have changed th

Re: [DISCUSS] KIP-584: Versioning scheme for features

itpick is that Kafka generally doesn't use "get" in the function names of accessors. (Kowshik): Done, I have changed the KIP. By 'interface', I just meant interface from a pseudocode standpoint (i.e. it was just an abstraction providing at least the specified behavior). Since that w

  1   2   >