Re: BP-68 - Delete cookie as part of decommission API

2024-09-09 Thread lushiji(apache)
Let me understand: is it to delete only the /api/v1/autorecovery/decommission API? then how to handle the command bin/bookkeeper shell decommissionbookie [-bookieid ] ? Personally, I think if there is a problem with the /api/v1/autorecovery/decommission API, why not fix this API instead of delet

Re: BP-68 - Delete cookie as part of decommission API

2024-09-11 Thread lushiji(apache)
, > Karthick > > On Mon, Sep 9, 2024 at 1:13 PM lushiji(apache) wrote: > > > Let me understand: is it to delete only the > > /api/v1/autorecovery/decommission API? then how to handle the command > > bin/bookkeeper shell decommissionbookie [-bookieid ] ? >

Re: question about the BookKeeper Proposals (BP) process

2024-09-15 Thread lushiji(apache)
Let me summarize Enrico's conclusion: 1. The BookKeeper Proposals (BP) process is: directly initiate a VOTE thread (without DISSCUSSION thread) 2. Constraint scope: that votes from BookKeeper's committers and BookKeeper's PMC are binding I think this topic is too divergent, I have summarized it to

Re: [VOTE] Change Default Value of readOnlyModeOnAnyDiskFullEnabled

2024-11-20 Thread lushiji(apache)
+1 (binding) On Mon, Nov 18, 2024 at 6:15 PM xiangying meng wrote: > Dear Bookkeeper Community, > > I would like to initiate a vote on the recent discussion regarding > changing the default value of the `readOnlyModeOnAnyDiskFullEnabled` > feature to true. You can find the details of the discuss

Re: [DISCUSS] Change Default Value of readOnlyModeOnAnyDiskFullEnabled

2024-11-17 Thread lushiji(apache)
+1 (non-binding) At least combined with the current features of bookkeeper, readOnlyModeOnAnyDiskFullEnabled should be enabled by default. If a single disk is full and it is not switched to read-only, the writeCache will only make the situation worse as the amount increases. On Sat, Nov 16, 2024

Re: [DISCUSS] BookKeeper 4.18.0 release

2025-04-08 Thread lushiji(apache)
+1 I understand that this is a certain range of version iterations, not just 4555 and 4512. On Wed, Apr 2, 2025 at 6:59 PM Yong Zhang wrote: > Hi all, > > The 4.17.0 has been released for 6 months, we have some > new improvements such as [1], and dependency updates such > as [2]. I want to start

Re: [DISCUSS] Upgrading BookKeeper to RocksDB 9.9.3 in 4.18.0 release

2025-04-18 Thread lushiji(apache)
+1 Great Jobs, Thanks On Thu, Apr 17, 2025 at 4:22 PM Lari Hotari wrote: > Hello BookKeeper community, > > I'd like to propose upgrading our RocksDB dependency from the current > 7.10.2 version to 9.9.3. > Among all 9.x versions, I specifically chose 9.9.3 since it's > currently the most recent

Re: [DISCUSS] Upgrading BookKeeper to RocksDB 9.9.3 in 4.18.0 release

2025-04-22 Thread lushiji(apache)
For the upgrade of RocksDB 9.9.3, I wonder if two emails can be sent to follow up 4.18.0 and 4.17.2. I feel that this is a bit confusing. It may be clearer to send two emails to follow up separately. Or other versions may also need this and follow up with the same email. On Tue, Apr 22, 2025 at 6

Re: Many patches pending review !

2025-02-13 Thread lushiji(apache)
+1 OK, no problem On Fri, Feb 14, 2025 at 3:46 AM Enrico Olivelli wrote: > Hello BookKeepers, > > I am preparing the report for the ASF Board and I have noticed that we have > a growing backlog of PRs. > > https://github.com/apache/bookkeeper/pulls > > Please take some time to review the pending

[VOTE] Release 4.16.7, release candidate #0

2025-06-24 Thread lushiji(apache)
Hi everyone, Please review and vote on the release candidate #0 for the version 4.16.7, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) The complete staging area is available for your review, which includes: * Release notes [1] * The of

Re: [DISCUSS] BookKeeper 4.17.2 release

2025-06-23 Thread lushiji(apache)
I(Steven Lu) have already started preparing 4.17.2 releases. https://github.com/apache/bookkeeper/pull/4622 Thanks On Fri, Jun 20, 2025 at 8:17 PM Lari Hotari wrote: > It looks like Steven Lu has already started preparing 4.17.2 and 4.16.7 > releases. > https://github.com/apache/bookkeeper/pull/

Re: [DISCUSS] BookKeeper 4.16.7 release

2025-06-24 Thread lushiji(apache)
I(Steven Lu) have already started preparing 4.16.7 releases. https://github.com/apache/bookkeeper/pull/4621 On Tue, Oct 15, 2024 at 2:28 PM Enrico Olivelli wrote: > +1 > > Enrico > > Il giorno mar 15 ott 2024 alle ore 05:34 Wenbing Shen < > oliver.shen...@gmail.com> ha scritto: > > > +1 > > > >

[VOTE] Release 4.17.2, release candidate #0

2025-06-25 Thread lushiji(apache)
Hi everyone, Please review and vote on the release candidate #0 for the version 4.17.2, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) The complete staging area is available for your review, which includes: * Release notes [1] * The of

[ANNOUNCE] Apache BookKeeper 4.17.2 released

2025-07-07 Thread lushiji(apache)
The Apache BookKeeper team is proud to announce Apache BookKeeper version 4.17.2. Apache BookKeeper is a scalable, fault-tolerant, and low-latency storage service optimized for real-time workloads. It has been used for a fundamental service to build reliable services. It is also the log segment st

[ANNOUNCE] Apache BookKeeper 4.16.7 released

2025-07-07 Thread lushiji(apache)
The Apache BookKeeper team is proud to announce Apache BookKeeper version 4.16.7. Apache BookKeeper is a scalable, fault-tolerant, and low-latency storage service optimized for real-time workloads. It has been used for a fundamental service to build reliable services. It is also the log segment st

Re: [VOTE] Release 4.16.7, release candidate #0

2025-07-02 Thread lushiji(apache)
The vote is now closed, and the release was approved with 3 binding votes. I will continue with the following steps. Votes: - Enrico Olivelli (binding) - Andrey Yegorov (binding) - Jia Zhai (binding) - Wenbing Shen Thank you all for verifying and voting! On Wed, Jun 25, 2025 at 9:42 AM lushiji

Re: [VOTE] Release 4.17.2, release candidate #0

2025-07-02 Thread lushiji(apache)
The vote is now closed, and the release was approved with 3 binding votes. I will continue with the following steps. Votes: - Enrico Olivelli (binding) - Andrey Yegorov (binding) - Jia Zhai (binding) - Wenbing Shen Thank you all for verifying and voting! On Thu, Jun 26, 2025 at 8:55 AM lushiji