Now, if the message's metadata does not set a broker side timestamp, the
ledger expiration check is based on the client's publish time.
When the client machine's clock is incorrect (eg: set to 1 year later) ,
the ledger can not be cleaned up. Issue
https://github.com/apache/pulsar/issues/21347
`A
Hi Pulsar Community,
This thread is to start the vote for PIP 255.
After discussion, we believe that it is a better way to plug-in the
partition assignment strategy,
and let customers complete the specific implementation.
So the title is change from "Assign topic partitions to bundle by round
rob
Hi all,
I created a proposal to
assign topic partitions to bundles by round robin:
https://github.com/apache/pulsar/issues/19806
It is already running in our production environment,
and it has a good performance.
Thanks!
Hi folks,
I'd like to start a vote for the PIP-219: Support full scan and trim ledger
(
https://github.com/apache/pulsar/issues/18128)
The discussion can be found here:
https://lists.apache.org/thread/wy8sqs2fdmw3kcdfos7t1ztpccfdmv72
Best regards.
linlin
Hi all,
I have drafted PIP-219: Support full scan and trim ledger
PIP link:
https://github.com/apache/pulsar/issues/18128
Here's a copy of the contents of the GH issue for your references:
### Motivation
Broker uses the `Trimledgers` thread to clean up outdated ledgers. During
cleaning, each B
The Apache Pulsar Project Management Committee (PMC) has invited Aloys Zhang
(https://github.com/aloyszhang) to become a committer and we are pleased to
announce that he has accepted.
Aloys Zhang joined the Pulsar community in June 2020 and contributed a lot
of commits
to the community, includin
The Apache Pulsar team is proud to announce Apache Pulsar version 2.8.2.
Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor management
for
subsc
This is the second release candidate for Apache Pulsar, version 2.8.2
It fixes the following issues:
https://github.com/apache/pulsar/issues?q=label%3Acherry-picked%2Fbranch-2.8+label%3Arelease%2F2.8.2+is%3Aclosed
*** Please download, test and vote on this release. This vote will stay open
for at
This is the first release candidate for Apache Pulsar, version 2.8.2.
It fixes the following issues:
https://github.com/apache/pulsar/issues?q=label%3Acherry-picked%2Fbranch-2.8+is%3Aclosed+label%3Arelease%2F2.8.2
*** Please download, test and vote on this release. This vote will stay open
for at
The Apache Pulsar Project Management Committee (PMC) has invited Marvin Cai
https://github.com/MarvinCai to become a committer and we are pleased to
announce that he has accepted.
Marvin has joined the community for more than 1 year now and he is active in
the Pulsar community for more than 6 mont
+1
Enrico Olivelli 于2021年11月1日周一 下午5:47写道：
> +1 (binding)
>
>
> Thanks
> Enrico
>
> Il Lun 1 Nov 2021, 09:50 PengHui Li ha scritto:
>
> > I would like to start a VOTE for PIP 106: Negative acknowledgment
> backoff
> >
> > The issue for this PIP is here
> >
> > https://github.com/apache/pulsar/
Hi all:
Now, Broker limits the rate of producing messages by setting
`channel.setAutoRead(false)`. But no exception is returned to the client,
or any log is printed, which makes it very difficult for us to troubleshoot
the problem.
The client timeout when sending messages and the connection will b
Hi all,
I hope you've all been doing well. It has been more than one month since we
released the Apache Pulsar 2.8.1. We have a lot of fixes already merged. So
I would like to start to prepare our next patch release in the next few
days.
You can find the whole change list of the 2.8.2 release fro
Hi Pulsar Community,
I would like to start a VOTE for PIP - Support pluggable entry filter in
Dispatcher.
The issue for this PIP is here:
https://github.com/apache/pulsar/issues/12269
Please VOTE within 72 hours.
Thanks,
Lin Lin
# Motivation
There are many users who need to use tag messages. The implementation of
this part has also been discussed before：
https://lists.apache.org/list.html?*@pulsar.apache.org:lte=2y:Proposal%20for%20Consumer%20Filtering%20in%20Pulsar%20brokers
I suggest to plug-in the Dispatcher, so that
Creating a topic will first check whether the topic already exists.
The verification will read all topics under the namespace, and then
traverse these topics to see if the topic already exists.
When there are a large number of topics under the namespace(about 300,000
topics),
less than 10 topics ca
Hi, All
I have prepared a PIP for the Topic policy across multiple clusters.
Please take a look and let me know what you think.
I would really appreciate it.
Best Regards,
Lin Lin
===
clusters
-
Status:
-
Aut
Hi, All
I have prepared a PIP for the Topic policy across multiple clusters.
Please take a look and let me know what you think.
I would really appreciate it.
Best Regards,
Lin Lin
===
Topic policy across multiple clusters
-
Status: Pr
rashes and recovers the managed ledger, the cursor>
> > ledger is not writable anymore. Are you going to create a new cursor
ledger>
> > and copy all the entries from the old cursor ledger to the new one?>
> >>
> > It would be good if you can clarify these two que
. Are you going to create a new cursor
ledger>
> and copy all the entries from the old cursor ledger to the new one?>
>
> It would be good if you can clarify these two questions.>
>
> - Sijie>
>
> On Sun, Jan 17, 2021 at 9:48 PM linlin wrote:>
>
> > Hi, com
Hi, community:
Recently we encountered some problems when using individual
acknowledgments, such as:
when the amount of acknowledgment is large, entry writing fails; a large
amount of cache causes OOM, etc.
So I drafted a PIP in `
https://docs.google.com/document/d/1uQtyb8t6X04v2vrSrdGWLFkuCkBc
21 matches
Mail list logo
