-1
There was a thread leak in MLTransactionMetadataStore which also impacts
production code.
It is fixed by https://github.com/apache/pulsar/pull/14524 which is now merged
to master branch. The thread leak resulted in a memory leak in tests and that's
how I noticed it.
The thread leak was also
Thanks Lari,
I have cherry-picked https://github.com/apache/pulsar/pull/14524 into
branch-2.10 and will
send out the new RC tomorrow.
Penghui
On Wed, Mar 2, 2022 at 8:30 PM Lari Hotari wrote:
> -1
>
> There was a thread leak in MLTransactionMetadataStore which also impacts
> production code.
>
Hi, Zixuan
Thanks for creating this PIP. Here are my thoughts.
> CursorInfo compression format
>
> [MAGIC_NUMBER] + [METADATA_SIZE] + [METADATA_PAYLOAD] +
> [MANAGED_CURSOR_INFO_PAYLOAD]
>
> MAGIC_NUMBER: Ox4779
Since we change the ManagedCursorInfo data format here. How do we
handle the old da
+1
On Tue, Mar 1, 2022 at 6:47 PM Guangning E wrote:
> Welcome to vote to verify it, thanks.
>
> Thanks,
> Guangning
>
> Guangning E 于2022年2月28日周一 22:12写道：
>
> > Hi everyone,
> > Please review and vote on the release candidate #2 for the version 1.6.0,
> > as follows:
> > [ ] +1, Approve the re
Hi Pulsar Community,
I create a proposal that support ManagedCursorInfo compression.
The proposal can be found: https://github.com/apache/pulsar/issues/14395
Motivation
The cursor data is managed by ZooKeeper/etcd metadata store. When
cursor data becomes more and more, the data size will incr
Update proposal link: https://github.com/apache/pulsar/issues/14529
Zixuan Liu 于2022年3月2日周三 12:41写道：
> Hi Pulsar Community,
>
>
> I create a proposal that support ManagedCursorInfo compression.
>
> The proposal can be found: https://github.com/apache/pulsar/issues/14395
>
>
> Motivation
>
> The
Thanks for identifying the issue and the fix, Enrico.
I am closing this vote and will start preparing RC 4.
- Michael
On Wed, Mar 2, 2022 at 1:22 AM Enrico Olivelli wrote:
>
> Michael,
>
> Il giorno mar 1 mar 2022 alle ore 12:47 Enrico Olivelli
> ha scritto:
> >
> > I have sent a PR with the
HI folks,
I found your email from the apache pulsar website. I need your help with the
following problem that we are facing
Lets say I have a publisher which ran normally first and produced 20 messages
to the topic
import org.apache.pulsar.client.api.Producer;
import org.apache.pulsar.client.a
vip32 commented on issue #283:
URL: https://github.com/apache/pulsar-manager/issues/283#issuecomment-1057387412
pfoeh, that was hard, This worked for me eventually
docker-compose
```
pulsar:
image: apachepulsar/pulsar:latest
container_name: shop_pulsar
com
Hi Andras Beni,
Thanks for your detailed proposal. I agree that the regex consumer is
a good candidate for optimization. Were there any alternative
solutions you considered when looking to optimize the regex consumer,
and if so, will you describe them?
One of my concerns is that this feature only
Paul-TT opened a new pull request #8:
URL: https://github.com/apache/pulsar-site/pull/8
This pull request addresses fixes or changes made to the site based on
feedback given in the Pulsar website channel on slack. Those comments were
compiled into a google doc.
https://docs.google.com/do
> The geo-replication's configuration can be centralized by using
> one configuration store. But that doesn't change anything, we should
> provide the same behavior for both centralized and decentralized
> configuration store.
Perhaps I misused the word decentralized. I meant that the challenge
co
Hi, Guangning
It seems that we have to upgrade version of pulsar-client-node to 1.6.2 because
1.6.0 and 1.6.1 already exist on the npm registry.
https://www.npmjs.com/package/pulsar-client/v/1.6.0
https://www.npmjs.com/package/pulsar-client/v/1.6.1
Once a package has been uploaded to the npm reg
dave2wave commented on pull request #33:
URL: https://github.com/apache/pulsar-adapters/pull/33#issuecomment-1057514874
I'm curious about the choice of pulsar 2.8.2 and versioning here. Is this
test for the main branch or other branches?
--
This is an automated message from the Apache Gi
dlg99 commented on pull request #33:
URL: https://github.com/apache/pulsar-adapters/pull/33#issuecomment-1057517761
@dave2wave 2.8.2 was the latest for 2.8.x. Bumping it here was needed to
bump some other dependencies and to remove a few CVEs + remove some false
alarms for CVEs.
pul
urfreespace commented on a change in pull request #8:
URL: https://github.com/apache/pulsar-site/pull/8#discussion_r818240877
##
File path: site2/website-next/src/theme/Navbar/index.js
##
@@ -307,13 +307,7 @@ function Navbar() {
setVersion(latestStableVersion);
Thank you for the reminder, I got it, I want to open the vote for 1.6.2
candidate 1 directly next time, what do you think @Hiroyuki Sakai, does
anyone have a different suggestion?
Thanks,
Guangning
Hiroyuki Sakai 于2022年3月3日周四 07:33写道：
> Hi, Guangning
>
> It seems that we have to upgrade version
Thank you for your feedback.
Forward compatibility is required:
1. Get CursorInfo from the metadata store: We will check the cursor data
header, if it is compressed, we will parse the bytes data by compressed format,
otherwise we will parse the cursor data directly by the original way.
2. Add
On Wed, Mar 2, 2022 at 2:15 PM Michael Marshall wrote:
> > A new class, org.apache.pulsar.TopicsListService will keep track
> > of watchers and will listen to changes in the metadata.
>
> I think we should avoid creating a new service to distribute
> notifications to consumers. Instead, we should
+1
Thanks
Xiaolong Ran
PengHui Li 于2022年2月27日周日 13:04写道：
> +1
>
> Thanks,
> Penghui
>
> On Sat, Feb 26, 2022 at 11:59 AM Haiting Jiang
> wrote:
>
> > +1
> >
> > Thanks,
> > Haiting
> >
> > On 2022/02/26 02:53:23 Aloys Zhang wrote:
> > > Hi Pulsar Community,
> > >
> > > I would like to start a
Hi, Guangning
> open the vote for 1.6.2 candidate 1 directly next time
I agree with this.
Regards,
Hiroyuki
From: Guangning E
Sent: Thursday, March 3, 2022 11:16
To: us...@pulsar.apache.org ; Dev
; 酒井 宏行
Subject: Re: [VOTE] Pulsar Node.js Client Release 1.6.0
This is the third release candidate for Apache Pulsar, version 2.8.3.
It fixes the following issues:
https://github.com/apache/pulsar/compare/v2.8.2...v2.8.3-candidate-4
*** Please download, test and vote on this release. This vote will stay open
for at least 72 hours ***
Note that we are voting
22 matches
Mail list logo
