Il ven 21 lug 2017, 20:11 Sijie Guo ha scritto:
> Checked the code and also confirmed with Matteo:
>
> - if you are using V3 protocol, all the ByteBuf are unpooled because of the
> deserialization of protobuf. It already makes the copy of the memory coming
> from Netty. so there is not memory lea
Checked the code and also confirmed with Matteo:
- if you are using V3 protocol, all the ByteBuf are unpooled because of the
deserialization of protobuf. It already makes the copy of the memory coming
from Netty. so there is not memory leak even you don't iterate over the
enumeration.
- if you are
Il ven 21 lug 2017, 18:39 Sijie Guo ha scritto:
> On Jul 21, 2017 9:25 AM, "Enrico Olivelli" wrote:
>
> Il ven 21 lug 2017, 18:19 Sijie Guo ha scritto:
>
> > On Jul 21, 2017 12:59 AM, "Enrico Olivelli" wrote:
> >
> > Hi,
> > I have just file this issue
> > https://github.com/apache/bookkeeper/
On Jul 21, 2017 9:25 AM, "Enrico Olivelli" wrote:
Il ven 21 lug 2017, 18:19 Sijie Guo ha scritto:
> On Jul 21, 2017 12:59 AM, "Enrico Olivelli" wrote:
>
> Hi,
> I have just file this issue
> https://github.com/apache/bookkeeper/issues/271
>
> After the switch to Netty 4 I noticed this "API cha
Il ven 21 lug 2017, 18:19 Sijie Guo ha scritto:
> On Jul 21, 2017 12:59 AM, "Enrico Olivelli" wrote:
>
> Hi,
> I have just file this issue
> https://github.com/apache/bookkeeper/issues/271
>
> After the switch to Netty 4 I noticed this "API change", that is very
> important to be documented and/
On Jul 21, 2017 9:17 AM, "Enrico Olivelli" wrote:
Il ven 21 lug 2017, 16:55 Enrico Olivelli ha scritto:
> (I am writing comments and proposals on the issue, I don't know where is
> the best place to talk)
> https://github.com/apache/bookkeeper/issues/271
>
>
> I think that we could break existi
On Jul 21, 2017 12:59 AM, "Enrico Olivelli" wrote:
Hi,
I have just file this issue
https://github.com/apache/bookkeeper/issues/271
After the switch to Netty 4 I noticed this "API change", that is very
important to be documented and/or to be addresses.
I think documentation is important in this
Il ven 21 lug 2017, 16:55 Enrico Olivelli ha scritto:
> (I am writing comments and proposals on the issue, I don't know where is
> the best place to talk)
> https://github.com/apache/bookkeeper/issues/271
>
>
> I think that we could break existing downstream applications, we must
> address this p
(I am writing comments and proposals on the issue, I don't know where is
the best place to talk)
https://github.com/apache/bookkeeper/issues/271
I think that we could break existing downstream applications, we must
address this problem
I think that we should change in a braking way the readEntri
Can we also add some stats around this to track these. ? Discipline around
memory release is new concept to Java world.
On Fri, Jul 21, 2017 at 12:59 AM Enrico Olivelli
wrote:
> Hi,
> I have just file this issue
> https://github.com/apache/bookkeeper/issues/271
>
> After the switch to Netty 4
Hi,
I have just file this issue
https://github.com/apache/bookkeeper/issues/271
After the switch to Netty 4 I noticed this "API change", that is very
important to be documented and/or to be addresses.
Inside LedgerEntry object we retain a ByteBuf, which is turn is
automatically 'released' only in
11 matches
Mail list logo
