,
Matteo Merli
/bookie/EntryLogTest.java
488f4bf
Diff: https://reviews.apache.org/r/33061/diff/
Testing
---
Thanks,
Matteo Merli
,
Matteo Merli
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40223/#review106374
---
Ship it!
Ship It!
- Matteo Merli
On Nov. 12, 2015, 9:53 a.m
This is the first release candidate for Apache BookKeeper, version 4.3.2.
It fixes the following issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12333529=Html=12311293
*** Please download, test and vote by November 16th 2015, 10:00 GMT.
Note that we are voting upon the
, at 06:31, Rakesh R rake...@huawei.com wrote:
Welcome Matteo Merli, thanks for all your great work and congratulations!
Best Regards,
Rakesh
-Original Message-
From: Sijie Guo [mailto:si...@apache.org]
Sent: 07 July 2015 10:46
To: dev@bookkeeper.apache.org
Cc: Matteo
This is the second release candidate for Apache BookKeeper, version 4.3.2.
It fixes the following issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12333529=Html=12311293
*** Please download, test and vote by November 21th 2015, 10:00 GMT.
Note that we are voting upon the
The Apache BookKeeper team is proud to announce Apache BookKeeper version
4.3.2.
This is the second release of Apache BookKeeper as an Apache Top Level
Project.
The BookKeeper project is made up of a distributed logging service called
BookKeeper and a distributed publish/subscribe system build
+1
I agree with Ivan
Matteo
On Thursday, November 26, 2015 12:53 AM, Ivan Kelly
wrote:
+1
I'd go even further and just remove it from the tree. There are no new
contributions going into it. The hedwig src for 4.3 is pretty much the
same as the hedwig src for 4.2
ldn't compile.
>
> - Sijie
>
> On Thu, Nov 12, 2015 at 11:59 PM, Matteo Merli <mme...@apache.org> wrote:
>
>> This is the first release candidate for Apache BookKeeper, version 4.3.2.
>>
>> It fixes the following issues:
>>
>> https:/
Rithin,
I've assigned you the Jira
On Wed, Jun 8, 2016 at 1:48 PM Enrico Olivelli wrote:
> Good catch!
> This is the issue https://issues.apache.org/jira/browse/BOOKKEEPER-881
>
> Enrico
>
>
> Il Mer 8 Giu 2016 20:09 Rithin Shetty ha scritto:
>
> > We
I was interested in trying something in this area, but never actually got
to do it.
A few random notes:
1. My suspicion, with no backing data at this point, is that simply
skipping the fsync
for "non-durable" ledgers might not give a big improvement, just a bit
less latency
for
'd better to not to change it if it isn't
> > a problem.
Reverted to original logic
- Matteo
-------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/33096/#review84268
-
Hi Arun,
what is your use case for waiting until the entries are "flushed" into the
entry logs?
Once the ledger.addEntry() operation completes, the entries are guaranteed
to have been written and fsynced on the journal device, from where they
will be recovered in case the bookie crashes before
Arun, I've added you to Jira.
On Thursday, March 10, 2016 1:46 AM, Arun M. Krishnakumar
wrote:
Hi Sijie,
Could you please add 'arunm...@gmail.com' as well to this role ? I will likely
need to go through the same process shortly.
Thanks,
Arun
> On Mar 10, 2016,
command. I am interested in the second part.)
> > > > > >
> > > > > > Thanks,
> > > > > > Arun
> > > > > >
> > > > > > On Fri, Feb 26, 2016 at 1:05 PM, Arun M. Krishnakumar <
> > > > > arunm...@gmail.com>
Flavio,
I think there are some substantial improvements in some areas, here are few
examples of non bug-fix changes:
BOOKKEEPER-841: Bookie should calculate ledgers map writing a new entry log
file
(Save a lot a read IO on bookie restart with at lot of data stored)
BOOKKEEPER-889: BookKeeper
I usually do that but forgot on that one PR.
OTOH, it might be good to extend the merge script (dev/bk-merge-pr.py) to
automatically leave a comment on the Jira with info on the committer,
reviewers, etc..
Matteo
On Sat, Apr 9, 2016 at 9:07 AM Sijie Guo wrote:
> Yup. We
+1
On Tue, Mar 8, 2016 at 10:23 AM Robin Dhamankar wrote:
> +1
> On Mar 8, 2016 10:22 AM, "Uma gangumalla" wrote:
>
> > +1
> >
> > Regards,
> > Uma
> >
> > On Mon, Mar 7, 2016 at 9:57 PM, Sijie Guo wrote:
> >
> > > Since Hedwig has
port patch? Can you please share it??
> What kind of operations can be performed on that port??
>
> Thanks,
> JV
>
> On Tue, Mar 1, 2016 at 11:56 PM, Matteo Merli <mme...@yahoo-inc.com.invalid
> >
> wrote:
>
> > Sijie,
> > we have a similar tool in our in
,
> Arun
>
> On Thu, Apr 21, 2016 at 9:28 AM, Matteo Merli <mme...@apache.org> wrote:
>
> > Hi all,
> >
> > I think we are very close to the release 4.4 and there are still just 4
> > jiras pending, with pull requests available (
> > https://github.co
Probably SyncCounter was introduced before CountdownLatch was available in
jdk. I think it should be good to switch to countdown latch.
On Fri, Apr 22, 2016 at 9:28 AM Venkateswara Rao Jujjuri
wrote:
> I am mostly concerned about this logic in block() which makes us
>
y 13, 2016 at 3:34 PM, Sijie Guo <si...@apache.org> wrote:
>
> > +1.
> >
> > verified the binary package. run local bookies.
> > verified the source package. build is good
> > verified the signatures.
> > verified LICENSE.
> >
>
Here are the vote results
+3 from PMC members (Flavio, Sijie, Uma)
+2 (Matteo, Enrico)
No -1s.
I'll proceed shortly with the release.
Matteo
On Sun, May 15, 2016 at 8:56 AM Matteo Merli <matteo.me...@gmail.com> wrote:
> +1 from me as well
>
> Checked tests / packages / signat
This is the first release candidate for Apache BookKeeper, version 4.4.0.
It fixes the following issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311293=12325566
*** Please download, test and vote by May 10th 2016, 10:00 GMT.
Note that we are voting upon the source
Sijie, I think I don't have write access to wiki. Can you add me? I'll
update the release process page
On Thu, May 5, 2016 at 11:16 AM Sijie Guo wrote:
> +1, go for it. Could you also update the wiki page for release process?
>
> - Sijie
>
rote:
> +1 (non binding)
>
> Ran unit tests on Linux/Oracle jdk 1.8.0_77
>
> Ran internal Majordodo Unit tests
>
> -- Enrico
>
> 2016-05-05 18:49 GMT+02:00 Matteo Merli <mme...@apache.org>:
>
> > This is the first release candidate for Apache BookKe
Hi all,
we should have all the changes planned for 4.4 release already merged in
master and build seems to be good.
If there are no objections or suggestions for Jiras that you think should
be considered for 4.4 inclusion, I will prepare a release candidate to
submit for voting.
Thanks,
Matteo
teswara Rao Jujjuri <jujj...@gmail.com
> > <javascript:;>> ha
> > > scritto:
> > >
> > > > +1.
> > > >
> > > > On Wed, May 4, 2016 at 9:04 AM, Sijie Guo <si...@apache.org
> > <javascript:;>> wrote:
> > >
We've just open-sourced Pulsar! This is a pub-sub messaging solution with
the necessary Yahoo scale, performance,
and feature requirements to provide messaging as a hosted service,
supporting a million topics.
Pulsar uses BookKeeper as the building block for the messages durable
storage.
You can
On Wed, Oct 26, 2016 at 11:45 AM Venkateswara Rao Jujjuri
wrote:
> - Ledgers are unique across multiple clusters. Useful if storage tiers with
> different stores are employed.
>
For this you could combine the ledgerId with another 64bit id, that could
encode the rest of the
+1
On Tue, Nov 15, 2016 at 12:22 PM Yiming Zang
wrote:
> SGTM +1
>
> On Tue, Nov 15, 2016 at 10:34 AM, Venkateswara Rao Jujjuri <
> jujj...@gmail.com> wrote:
>
> > Sounds good.
> >
> > On Tue, Nov 15, 2016 at 1:41 AM Enrico Olivelli
> > wrote:
>
Hi all,
we're in the process to organize a BookKeeper meetup for the next Tue.
November 15th.
The event will be held in the Yahoo offices in Sunnyvale.
We would like to see if there is anyone, other than the usual suspects,
interested in talking about any BookKeeper related topic (eg: use
In this commit from the Yahoo branch we did a similar thing
https://github.com/yahoo/bookkeeper/commit/92e2f906f83d997b5cf5ffd2bcfcdbe53ca3bd04
The idea there was to have a CLI tool to dump the content of a ledger,
reading all the entries (or a subset of them) without triggering the ledger
https://goo.gl/iyRA6G
On Thu, Apr 6, 2017 at 8:05 AM Bobby Evans
wrote:
> What is the URL. I can never find it
>
>
> - Bobby
>
> On Thursday, April 6, 2017, 5:02:53 AM CDT, Enrico Olivelli <
> eolive...@gmail.com> wrote:Anyone on the Hangout ?
>
> 2017-04-05 14:19
+1
On Fri, Apr 21, 2017 at 7:06 AM Enrico Olivelli wrote:
> I wonder if we can start publishing the 4.5.0-SNAPSHOT binaries on
> Maven Central.
>
> This will help projects which want to try the upcoming version without
> dealing with custom local Maven Repositories.
>
> I
On Tue, Mar 7, 2017 at 10:10 AM Charan Reddy G
wrote:
> But due to the limitation of ZK (which is well documented thing in ZK
> https://zookeeper.apache.org/doc/r3.4.5/zookeeperProgrammers.html#ch_
> zkWatches), "Because watches are one time triggers and there is latency
> >
> > >Transparency - There will be a published cut-off date (AKA feature
> > >freeze) for the release and people will know about it in advance.
> > Hopefully
> > >this will remove the contention around which features make it.
> > >4.
> > >
> > >Quality - we've seen issues pop up in release candidates due to
> > >last-minute features that didn't have proper time to bake in. More
> > time
> > >between feature freeze and release will let us test more, document
> > more and
> > >resolve more issues.
> > >
> > >
> > > - Sijie
> > >
> >
> --
>
>
> -- Enrico Olivelli
>
--
Matteo Merli
<mme...@apache.org>
That's true, though I would swear that it was working just a couple of
hours ago. :)
--
Matteo Merli
<matteo.me...@gmail.com>
On Tue, Jul 18, 2017 at 4:23 PM, Edward Ribeiro <edward.ribe...@gmail.com>
wrote:
> FYI, the 'Documentation', 'Get Involved' and 'Project Info'
On Tue, Jul 25, 2017 at 2:57 PM, Ivan Kelly wrote:
> Is there an apache "team" in slack? it would save having to have
> multiple teams open if a person is involved in multiple projects. This
> would be especially useful for people who use slack in the browser. It
> would also
Sure, make sure to place it under the "content/" folder which is where
gitpubsub is expecting it to be.
--
Matteo Merli
<matteo.me...@gmail.com>
On Thu, Jul 27, 2017 at 10:27 AM, Sijie Guo <guosi...@gmail.com> wrote:
> I created a blank branch 'asf-site' for enabl
+1
--
Matteo Merli
<matteo.me...@gmail.com>
On Thu, Jul 27, 2017 at 11:06 AM, Enrico Olivelli <eolive...@gmail.com>
wrote:
> +1 non binding
>
> Enrico
>
> Il gio 27 lug 2017, 20:02 Sijie Guo <guosi...@gmail.com> ha scritto:
>
> > Start a vote thread f
ttps://github.com/apache/bookkeeper/pull/402
> [2] https://dist.apache.org/repos/dist/dev/bookkeeper/4.5.0-rc0/
> [3] https://repository.apache.org/content/repositories/
> orgapachebookkeeper-1012/
> [4] https://github.com/apache/bookkeeper/tree/release-4.5.0
>
> --
> Jvrao
>
] https://github.com/apache/bookkeeper/pull/402
> [2] https://dist.apache.org/repos/dist/dev/bookkeeper/4.5.0-rc0/
> [3] https://repository.apache.org/content/repositories/
> orgapachebookkeeper-1012/
> [4] https://github.com/apache/bookkeeper/tree/release-4.5.0
>
> --
> Jvrao
> ---
> First they ignore you, then they laugh at you, then they fight you, then
> you win. - Mahatma Gandhi
>
--
Matteo Merli
<mme...@apache.org>
My understanding is that fsync() forces the IO on the metadata even if the
file size has not changed, for example to update the access timestamp.
On Wed, May 10, 2017 at 4:47 PM Venkateswara Rao Jujjuri
wrote:
> Let me try to consolidate the discussion.
>
> 1. We need to
>>
>>
>>
>>> Anyway just trying broaden the discussion and if we have any doubt if
>>> java does fdatasync all the time.
>>>
>>> On Wed, May 10, 2017 at 4:57 PM, Matteo Merli <matteo.me...@gmail.com>
>>> wrote:
>>>
&g
I think there has been some confusion. Some of us "met" last Thursday,
since it was 2 weeks from the previous call.
On Thu, May 11, 2017 at 3:46 AM Enrico Olivelli wrote:
> I have just created the wiki page for next meeting
>
>
>
ut the scenario in question is for EntryLogger.logChannel and
> in GarbageCollectorThread.doCompactEntryLogs codepath. Here we just keep
> adding entries to the EntryLogger.logChannel and flush it before deleting
> the compacted entrylog.
>
> Thanks,
> Charan
>
> On Wed, May 10, 2017 at 11:35 AM,
To add more context, this topic was discussed recently at ApacheCon.
See this talk https://www.youtube.com/watch?v=yWurOHvm5WM
Relevant portion start at 18:00.
In short, they are saying that the
ASF is trying to leverage Github more and more in the future.
Matteo
On Thu, Jun 1, 2017 at 4:48 PM
+1
Having issues and PR in one tool is a great plus.
If this proposal is accepted, we should also ask INFRA to allow to assign
issues/PRs to committers/contributors and to create labels that fit our
workflow.
On Thu, Jun 1, 2017 at 3:03 PM Sijie Guo wrote:
> My vote on
> Kishore is seeing epoll compatibility issues with nio on netty 4.1.
What do you guys mean by incompatibility?
Netty can have the event loop to work either with the regular JDK nio
select or by using JNI to call epoll directly, but it should be either
everything goes with NIO or everything goes
wiki on GitHub
> http://eolivelli.blogspot.it/2017/09/herddb-distributed-jvm-embeddable.html
>
> The code is open source and you can find it as usual on GitHub
> https://github.com/diennea/herddb
>
> Any contribution will be welcome !
>
> Cheers
>
> Enrico Olivelli
>
--
Matteo Merli
<mme...@apache.org>
bookkeeper-dev/201710.mbox/ajax/%
> > 3CCAO2yDyarL1%2Bf7AWB89NfUH3Ji35RZVaR-CmLYV16i-1RW%2BA8Lg%40mail.
> > gmail.com%3E
> >
> > But we never formally called a vote, so here's the vote.
> >
> > The bylaws don't actually cover votes like this, so lets use lazy
> > majority, active committers.
> >
> > -Ivan
> >
>
--
Matteo Merli
<mme...@apache.org>
per.apache.org/docs/4.5.1/overview/releaseNotes/
>
> We would like to thank the contributors that made the release possible.
>
> Regards,
>
> The BookKeeper Team
>
--
Matteo Merli
<mme...@apache.org>
hanks,
> > Sijie Guo
> >
> > [1] https://github.com/apache/bookkeeper/pull/1518
> > [2]
> > https://dist.apache.org/repos/dist/dev/bookkeeper/bookkeeper-4.7.1-rc0/
> > [3]
> >
> >
> https://repository.apache.org/content/repositories/orgapachebookkeeper-1030/
> > [4] https://github.com/apache/bookkeeper/tree/v4.7.1-rc0
> >
>
--
Matteo Merli
pad each
> write to the journal out to the expected block size (i don't think we
> queried the actual size), which would ensure that you didn't try to
> rewrite a block, which could corrupt data if you failed in the middle
> of a rewrite. Of course, there's no guarantee that these t
operation is submitted to
> a ledger, it only ever operates on a single thread.
> If you look at LedgerHandle now, you have to jump around 4 files to
> deduce which thread methods like handleBookieFailure or
> sendAddSuccessCallbacks are called on, and even then you can't even be
> sure, so we wrap everything in synchronized when we don't really need
> to.
>
> -Ivan
>
--
Matteo Merli
gt; > >> > sha ea072c8f8b9d20651b513036c09f264ca5c7ec6e
> > > >> >
> > > >> > BookKeeper's KEYS file contains PGP keys we used to sign this
> > release:
> > > >> > https://dist.apache.org/repos/dist/release/bookkeeper/KEYS
> > > >> >
> > > >> > Please download these packages and review this release candidate:
> > > >> >
> > > >> > - Review release notes
> > > >> > - Download the source package (verify shasum, and asc) and follow
> > the
> > > >> > instructions to build and run the bookkeeper service.
> > > >> > - Download the binary package (verify shasum, and asc) and follow
> > the
> > > >> > instructions to run the bookkeeper service.
> > > >> > - Review maven repo, release tag, licenses, and any other things
> you
> > > >> think
> > > >> > it is important to a release.
> > > >> >
> > > >> > The vote will be open for at least 72 hours. It is adopted by
> > majority
> > > >> > approval, with at least 3 PMC affirmative votes.
> > > >> >
> > > >> > Thanks,
> > > >> > Sijie Guo
> > > >> >
> > > >> > [1] https://github.com/apache/bookkeeper/pull/1628
> > > >> > [2]
> > > >> >
> > >
> https://dist.apache.org/repos/dist/dev/bookkeeper/bookkeeper-4.7.2-rc0/
> > > >> > [3]
> > > >> >
> > > >> >
> > > >>
> > >
> >
> https://repository.apache.org/content/repositories/orgapachebookkeeper-1031/
> > > >> > [4] https://github.com/apache/bookkeeper/tree/v4.7.2-rc0
> > > >> >
> > > >>
> > > >
> > >
> >
>
--
Matteo Merli
> > Sijie Guo
> >
> > [1] https://github.com/apache/bookkeeper/pull/1330
> > [2] https://dist.apache.org/repos/dist/dev/bookkeeper/
> > bookkeeper-4.7.0-rc1/
> > [3] https://repository.apache.org/content/repositories/
> > orgapachebookkeeper-1029/
> > [4] https://github.com/apache/bookkeeper/tree/release-4.7.0
> >
> >
>
--
Matteo Merli
<mme...@apache.org>
, 2018 at 11:16 AM Sijie Guo <guosi...@gmail.com> wrote:
> On Sat, Mar 24, 2018 at 8:38 AM, Matteo Merli <mme...@apache.org> wrote:
>
> > While profiling the allocations of a BookKeeper client (from current
> > master) writing entries, I've noticed that there are mult
ght be worth to refactor OrderedScheduler or
OrderedSafeExecutor to avoid that overhead.
Thoughts?
Matteo
--
Matteo Merli
<mme...@apache.org>
re time to find
out potential issues before getting closer to Pulsar release timeline.
Matteo
--
Matteo Merli
<mme...@apache.org>
to call out Ivan Kelly & Jia Zhai for giving a big push of
porting many of the changes into BookKeeper and the BookKeeper community
for being very receptive and helpful in getting this load of changes back
into mainline.
Matteo
--
Matteo Merli
<mme...@apache.org>
created by that instance.
--
Matteo Merli
be very slow so not
to be useful in practice
--
Matteo Merli
+1
* Check binary, checksums, and ran a localbookie
* Source, checked rat and compiled with tests
--
Matteo Merli
On Fri, Nov 30, 2018 at 2:53 AM Sijie Guo wrote:
> Hi everyone,
>
> Please review and vote on the release candidate #0 for the version 4.7.3,
> as follows:
>
Thanks Enrico for calling this out.
Let me try to get a fix today for this. Otherwise let's go ahead with 4.9.1.
Thanks,
Matteo
--
Matteo Merli
On Mon, Mar 18, 2019 at 4:01 AM Enrico Olivelli wrote:
>
> Matteo and Ivan,
> I see this issue marked for 4.9.1
> https://githu
Hi Enrico,
looked into it but haven't found root cause yet.
Please proceed with release.
--
Matteo Merli
On Tue, Mar 19, 2019 at 5:43 AM Enrico Olivelli wrote:
>
> News?
>
> Enrico
>
> Il lun 18 mar 2019, 17:18 Matteo Merli ha scritto:
>>
>> Thanks Enrico for
+1 (binding)
(MacOS 10.14)
Verified:
* Signatures
* Source package build
* Binary with localbookie
* Client library jars in Maven
--
Matteo Merli
On Mon, Jan 28, 2019 at 10:21 PM Jia Zhai wrote:
>
> +1 (binding)
>
> Environment: macOS 10.14.2
>
>
> - verified 4 pa
ures and checksums
> > Checked RAT/Spotbugs on JDK8
> > Built on JDK8 + Linux, run tests
> > Run "standalone" mode and localbookie (with JDK8)
> > Compared tarballs with 4.9.1 onces, no significant changes (I have used
> > 'meld')
> >
> > Thank you Mat
+1
--
Matteo Merli
On Wed, May 8, 2019 at 6:47 PM Sijie Guo wrote:
>
> Hi all,
>
> Here is a draft for BookKeeper board report of May. Please take a look.
>
> If there is no objections, I will submit it today.
>
> ---
>
>
> ## Description:
>
> B
If that's ok, then I'll start preparing for 4.9.2.
--
Matteo Merli
On Fri, May 3, 2019 at 11:51 AM Enrico Olivelli wrote:
>
> Il ven 3 mag 2019, 19:01 Matteo Merli ha scritto:
>
> > Hi all,
> >
> > I wanted to check for opinions on starting a BK 4.9.2 release.
eeper/tree/v4.9.2-rc0
--
Matteo Merli
://github.com/apache/bookkeeper/pull/2022
Complete list of changes currently marked for 4.9.2:
https://github.com/apache/bookkeeper/issues?q=label%3Arelease%2F4.9.2+is%3Aclosed
Thoughts? Anything else that should go in?
--
Matteo Merli
+1 from me on Gradle.
The advantages in having very fast (and correct) incremental builds
are very nice.
I wouldn't expect major problems in setting up for Apache releases
since several other ASF projects are already using it.
Based on feedback on this, I'd also like to later start a similar
On Fri, Jan 8, 2021 at 2:15 PM Venkateswara Rao Jujjuri
wrote:
>
> > otherwise the write will timeout internally and it will get replayed to a
> new bookie.
> If Qa is met and the writes of Qw-Qa fail after we send the success to the
> client, why would the write replayed on a new bookie?
I
On Fri, Jan 8, 2021 at 8:27 AM Enrico Olivelli wrote:
>
> Hi Matteo,
> in this comment you are talking about an issue you saw when WQ is greater
> that AQ
> https://github.com/apache/bookkeeper/issues/2497#issuecomment-734423246
>
> IIUC you are saying that if one bookie is slow the client
Andrey, there are several PRs that would be good to get into 4.14. We
shouldn't just push everything out to 4.15.
Just a couple of examples:
* https://github.com/apache/bookkeeper/pull/2710
* https://github.com/apache/bookkeeper/pull/2698
--
Matteo Merli
On Fri, May 7, 2021 at 12:55 PM
+1 (binding)
Checked:
* Signatures
* Source package structure, and compile
* Binary package
* Running standalone bookie and client
--
Matteo Merli
On Fri, May 14, 2021 at 2:23 PM Andrey Yegorov
wrote:
>
> I do not hear voices against it so I assume everyone is ok with this
to be included in the imminent Pulsar
2.8.0 release, I think we should release a patch ASAP in order to
unblock that release.
If there are no objections, I'll move forward with the patch release.
Thanks,
Matteo
--
Matteo Merli
On Tue, May 25, 2021 at 6:00 AM Enrico Olivelli wrote:
> Before rushing to a release, isn't it better to wait for a couple of
> weeks in order to see
> if other people in the community find other problems on 4.14.0
As it is, the 4.14.0 release cannot be used by Pulsar. At the same
time, there
The vote is now closed and the release was approved with 6 +1s (4
binding and 2 non-binding);
Binding votes:
* Matteo
* Jia
* Sijie
* Enrico
Non-Binding votes:
* Yong
* Hang
Thank you.
Matteo
--
Matteo Merli
On Mon, May 31, 2021 at 5:47 AM hangc wrote:
>
> +1(non-b
ase-4.14.1-rc0
[5] f7a94422e44a7da6a5a8667853ad468bb0194642
Thank you,
Matteo
--
Matteo Merli
+1 We should do 4.14, carrying all the fixes that are there in master as well.
--
Matteo Merli
On Tue, May 4, 2021 at 11:57 AM Sijie Guo wrote:
>
> +1
>
> On Tue, May 4, 2021 at 2:22 AM Yunze Xu
> wrote:
>
> > Hello,
> > About 10 days ago I found a heap memory
is that this check is done before starting replicating
a ledger. If the copy process gets started, it will then continue
until done. A potential improvement here would be to even break the
copy of 1 ledger.
Matteo
--
Matteo Merli
On Sat, Aug 28, 2021 at 6:47 AM zhangao wrote:
>
> Maybe the idea
The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PMC affirmative votes.
Thanks,
Matteo
--
Matteo Merli
On Thu, Dec 16, 2021 at 10:18 PM Enrico Olivelli wrote:
>
> +1
>
> Especially if we have to deliver the upgrade of log4j2
BK 4.14 is including log4j 1.2.x, which has other vulnerabilities,
though not the log4shell one.
+1
Verified:
* Checksums
* Building
* Starting standalone bookie
Matteo
--
Matteo Merli
On Mon, Nov 1, 2021 at 8:42 AM Matteo Merli wrote:
>
> I think if the issue with Java 11 is in that test, we shouldn't block
> the release as this was probably already there before.
>
+1
Verified:
* Checksums
* Building
* Starting standalone bookie
--
Matteo Merli
On Fri, Nov 5, 2021 at 4:26 AM Enrico Olivelli wrote:
>
> +1 (binding)
>
> - verified signatures and digests
> - built from source, on JDK8 + Ubuntu
> - verified Apache RAT check
>
I think if the issue with Java 11 is in that test, we shouldn't block
the release as this was probably already there before.
We should instead make sure the BK CI is using Java 11 to run the
tests, to avoid this kind of issue.
Matteo
--
Matteo Merli
On Mon, Nov 1, 2021 at 7:08 AM Yong Zhang
There are few fixes in the 4.14 that would be good to release soon.
Given that the timeline for 4.15 can be quite long, I'd propose to
release one more patch release right now.
Let me know if there are other fixes to include.
Matteo
--
Matteo Merli
Closing this vote with 3 binding and 2 non-binding +1s :
Binding +1s:
* Matteo
* Enrico
* Jia
Non-Binding +1s:
* Nicolò
* Andrey
Thanks everyone,
Matteo
--
Matteo Merli
On Wed, Jan 5, 2022 at 5:16 AM Jia Zhai wrote:
>
> +1 (binding)
>
> - verified packages checksum an
On Thu, Dec 23, 2021 at 2:27 AM Enrico Olivelli wrote:
>
> Matteo,
> Are you preparing the release notes ?
> Which are the contents of the release ?
Added PR for release notes:
https://github.com/apache/bookkeeper/pull/2986
tively
> low. Idle, so that the full utilization of the write cache is not used;
>
> So I made the following changes:
> 1.Two write caches become multi-cache blocks;
> 2.All data directories share write cache resources;
>
> For BP and PR :
> https://github.com/apache/bookkeeper/iss
+1
Verified:
* Checksums
* Building
* Starting standalone bookie
Thanks,
Matteo
--
Matteo Merli
On Wed, May 4, 2022 at 8:53 AM Andrey Yegorov
wrote:
>
> Hi everyone,
>
> The vote has been out for 5 days - any feedback?
>
> On Fri, Apr 29, 2022 at 2:08 PM Andrey Yegorov
+1 (binding)
Very good addition!
--
Matteo Merli
On Tue, Oct 11, 2022 at 4:38 AM Enrico Olivelli wrote:
>
> Up
>
> We need 1 more binding vote from a PMC member
>
> Enrico
>
> Il Mar 27 Set 2022, 11:36 Nicolò Boschi ha scritto:
>
> > +1 (non binding)
> &
+1
--
Matteo Merli
On Mon, Mar 20, 2023 at 6:05 AM Hang Chen wrote:
> This is the vote for BP-62.
>
> ### Motivation
> The bookie server process add-entry requests pipeline:
> - Get one request from the Netty socket channel
> - Choose one thread to process the written
+1 binding
* Checked signatures
* Check localbookie and local perf tool
--
Matteo Merli
On Wed, Mar 29, 2023 at 7:06 AM Hang Chen wrote:
> Hi everyone,
> Please review and vote on the release candidate #2 for version 4.16.0,
> as follows:
> [ ] +1, Approve the release
[
https://issues.apache.org/jira/browse/BOOKKEEPER-841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matteo Merli updated BOOKKEEPER-841:
Attachment: 0001-BOOKKEEPER-841-Bookie-should-calculate-ledgers-map-w.patch
Updated
[
https://issues.apache.org/jira/browse/BOOKKEEPER-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14490478#comment-14490478
]
Matteo Merli commented on BOOKKEEPER-850:
-
Needs the method
1 - 100 of 288 matches
Mail list logo