bump
Jie crossover 于2024年6月24日周一 10:01写道：
> Hi, Pulsar Community.
>
> I would like to start the voting thread for PIP-363: Add callback
> parameters to the method:
> org.apache.pulsar.client.impl.SendCallback.sendComplete.
>
> PIP: https://github.com/apache/pulsar/pull/22940
> Discussion
+1 nonbinding
Jie crossover 于2024年6月24日 周一10:01写道：
> Hi, Pulsar Community.
>
> I would like to start the voting thread for PIP-363: Add callback
> parameters to the method:
> org.apache.pulsar.client.impl.SendCallback.sendComplete.
>
> PIP: https://github.com/apache/pulsar/pull/22940
>
Hi Jie,
Thanks, so we don't need to fix Skywalking, for OpenTelemetry-javaagent,
I'll create a PR to fix this.
Jie crossover 于2024年6月21日周五 17:52写道：
> Hi Jiuming,
>
> Good suggestion, done.
> --
> Best Regards！
> crossoverJie
>
>
> 太上玄元道君 于2024年6月21日周五 17:34写道：
>
ecause the data sent in batches cannot be obtained in the
> current pulsar-client, so when this feature is released, we need to add an
> agent based on the latest version in OTel and Skywalking.
>
> --
> Best Regards！
> crossoverJie
>
>
> 太上玄元道君 于2024年6月21日周五 13:30写道：
>
&
Hi Jie,
I support the PIP but there are something we need to consider:
OpenTelemetry-javagent[1] and Apache Skywalking-javaagent[2] enhanced
`SendCallback` to monitor sending messages, if we change the method sign,
the java-agents can't work.
It will be great that you can make it compatible, or,
+1 nonbinding
Thanks,
Tao Jiuming
Hang Chen 于2024年5月31日 周五08:47写道：
> Hi, all
>
> I would like to start the voting thread for PIP-355: Enhancing
> Broker-Level Metrics for Pulsar
>
> PIP: https://github.com/apache/pulsar/pull/22778
>
> Thanks
> Hang
>
+1
Baodi Shi 于2024年5月20日 周一18:48写道：
> Hi all, I push a pip to improve transaction message visibility for the
> peek-messages command.
>
> https://github.com/apache/pulsar/pull/22746
>
> Please feel free to leave your ideas.
>
>
> Thanks,
> Baodi Shi
>
+1 nonbinding
Thanks,
Tao Jiuming
thetumbled 于2024年5月14日 周二17:26写道：
> Hi, Pulsar Community.
> I would like to start the voting thread for PIP-347: add role field in
> consumer's stat.
> Proposal PR: https://github.com/apache/pulsar/pull/22564
> Implementation PR:
+1 nonbinding
Thanks,
Tao Jiuming
Yong Zhang 于2024年5月13日周一 10:57写道：
> Hi,
>
> I would like to start voting thread for PIP-350.
> https://github.com/apache/pulsar/pull/22688
>
> The implementation PR is:
> https://github.com/apache/pulsar/pull/22689
>
> Discuss thread:
>
looks good
Yong Zhang 于2024年5月10日周五 11:31写道：
> Hi all,
>
> I pushed a new proposal to allow to use -1 to disable
> the managedLedgerOffloadDeletionLagInMillis to not delete the data from
> bookkeeper.
>
> Please take a look and share your thoughts. Thanks!
>
> PIP:
+1 nonbinding
Thanks,
Tao Jiuming
Hang Chen 于2024年5月7日 周二11:25写道：
> Hi guys,
> I want to start voting for PIP-349.
>
> PIP: https://github.com/apache/pulsar/pull/22651
> PR: https://github.com/apache/pulsar/pull/22614
>
> DISCUSSION Thread:
>
+1 nonbinding
Thanks,
Tao Jiuming
Hang Chen 于2024年5月7日 周二11:27写道：
> Hi guys,
> I want to start voting for PIP-348.
>
> PIP: https://github.com/apache/pulsar/pull/22650
> PR: https://github.com/apache/pulsar/pull/22652
>
> DISCUSSION Thread:
>
FLAGs
Thanks,
Tao Jiuming
Enrico Olivelli 于2024年5月5日 周日13:44写道：
> daojun,
>
> Il giorno sab 4 mag 2024 alle ore 22:06 太上玄元道君 ha
> scritto:
>
> > it doesn't matter, we don't need to wait until offload finished when
> > loading topic, since offloading may take a lon
looks good
Hang Chen 于2024年5月5日 周日00:02写道：
> Hi guys,
> I proposed a new proposal to improve the TTL impact on system
> cursors. Please help take a look, thanks.
>
> PIP: https://github.com/apache/pulsar/pull/22651
>
> Thanks,
> Hang
>
it doesn't matter, we don't need to wait until offload finished when
loading topic, since offloading may take a long time.
it just trigger offloading, and we don't need to handle the result.
Enrico Olivelli 于2024年5月5日 周日02:41写道：
> Overall I think it is a good idea.
>
> What about adding a flag
It looks like https://github.com/apache/pulsar/pull/22562 is the
implementation PR and just introduces a `role` field in consumer stats.
It is acceptable and I agree with it.
Thanks,
Tao Jiuming
thetumbled 于2024年4月23日周二 16:23写道：
> Hi, pulsar community.
> I open a new PIP for finding out the
+1 nonbinding
Rajan Dhabalia 于2024年4月17日周三 01:08写道：
> Hi,
>
> I would like to start voting thread for PIP-327 which also addresses issue
> # https://github.com/apache/pulsar/issues/21751
>
> PIP design PR:
> https://github.com/apache/pulsar/pull/21752
>
bump
太上玄元道君 于2024年4月11日周四 18:20写道：
> Hi, Pulsar community,
>
> I'm opening this thread to discuss the retention policy for managed
> ledgers.
>
> Currently, the retention policy is defined as a time/size-based policy to
> retain messages in the ledger, but there is
of a
> large backlog quota (e.g., 100GB) to ensure they can revert to a position
> 10GB earlier, even if there isn't backlog in subscription.
>
> Regards,
> Yike
> ____
> From: 太上玄元道君
> Sent: Thursday, April 11, 2024 18:20
> To: dev@pulsar.ap
Hi, Pulsar community,
I'm opening this thread to discuss the retention policy for managed ledgers.
Currently, the retention policy is defined as a time/size-based policy to
retain messages in the ledger, but there is a difference between the
official documentation and the actual code
the limitation seems make no sense, after
http://github.com/apache/pulsar/pull/22472 merged, I'll try to fix it.
Thanks,
Tao Jiuming
Yike Xiao 于2024年4月10日 周三16:58写道：
> Here's a hint as to why this restriction was introduced.
> After reviewing the current implementation of the retention policy,
this case, if the broker tries to search the entry with a predicate and
> index. The managed
> ledger will search from the index first. Of course, if the relevant entry
> cannot be found in the index,
> just fall back to the "optimized full scan".
>
> Regards,
> Penghui
>
bump
太上玄元道君 于2024年3月20日 周三16:23写道：
> bump
>
> 太上玄元道君 于2024年3月19日 周二19:35写道：
>
>> Hi Pulsar community,
>>
>> This thread is to start a vote for PIP-345: Optimize finding message by
>> timestamp
>>
>> PIP: https://github.com/apache/pulsar/pull/2223
bump
太上玄元道君 于2024年3月19日 周二19:35写道：
> Hi Pulsar community,
>
> This thread is to start a vote for PIP-345: Optimize finding message by
> timestamp
>
> PIP: https://github.com/apache/pulsar/pull/22234
> Discuss thread:
> https://lists.apache.org/thread/5owc9os6wmy52zxbv07
Hi Pulsar community,
This thread is to start a vote for PIP-345: Optimize finding message by
timestamp
PIP: https://github.com/apache/pulsar/pull/22234
Discuss thread:
https://lists.apache.org/thread/5owc9os6wmy52zxbv07qo2jrfjm17hd2
Thanks,
Tao Jiuming
p`
> to
> > make it clear.
> >
> > Thanks,
> > Tao Jiuming
> >
> > Girish Sharma 于2024年3月15日周五 12:14写道：
> >
> > > One suggestion, I think you can make do with storing just begin
> > timestamp.
> > > Any search utilising th
On Fri, Mar 15, 2024, 9:39 AM 太上玄元道君 wrote:
>
> > bump
> >
> > 太上玄元道君 于2024年3月10日 周日06:41写道：
> >
> > > Hi Pulsar community,
> > >
> > > A new PIP is opened, this thread is to discuss PIP-345: Optimize
> finding
> > > message by t
bump
太上玄元道君 于2024年3月10日 周日06:41写道：
> Hi Pulsar community,
>
> A new PIP is opened, this thread is to discuss PIP-345: Optimize finding
> message by timestamp.
>
> Motivation:
> Finding message by timestamp is widely used in Pulsar:
> * It is used by the `pulsar-admin` to
+1 nonbinding
Matteo Merli 于2024年3月14日周四 09:45写道：
> PIP: https://github.com/apache/pulsar/pull/22178
>
> WIP PR: https://github.com/apache/pulsar/pull/22179
>
>
>
>
> --
> Matteo Merli
>
>
ese new ledger fields?
> I think you are asking to modify the main message logic which is highly
> optimized., but I’m not sure. Have you tried your code on your own
> hardware? Do you have performance comparisons of the normal flow?
>
> > On Mar 11, 2024, at 7:41 PM, 太上玄元道君 wrote:
bump
太上玄元道君 于2024年3月11日 周一17:55写道：
> bump
>
> 太上玄元道君 于2024年3月10日周日 06:41写道：
>
>> Hi Pulsar community,
>>
>> A new PIP is opened, this thread is to discuss PIP-345: Optimize finding
>> message by timestamp.
>>
>> Motivation:
>>
bump
太上玄元道君 于2024年3月10日周日 06:41写道：
> Hi Pulsar community,
>
> A new PIP is opened, this thread is to discuss PIP-345: Optimize finding
> message by timestamp.
>
> Motivation:
> Finding message by timestamp is widely used in Pulsar:
> * It is used by the `pulsar-admin` to
Hi Pulsar community,
A new PIP is opened, this thread is to discuss PIP-345: Optimize finding
message by timestamp.
Motivation:
Finding message by timestamp is widely used in Pulsar:
* It is used by the `pulsar-admin` tool to get the message id by
timestamp, expire messages by timestamp, and
+1 nonbinding
Zixuan Liu 于2024年3月6日 周三23:04写道：
> Hello,
>
> A new proposal to improve the CLI user experience.
>
> PIP: https://github.com/apache/pulsar/pull/22181
> Discussion thread:
> https://lists.apache.org/thread/ydg1q064cd11pxwz693frtk4by74q32f
>
> PR:
＋1
Enrico Olivelli 于2024年3月3日 周日16:58写道：
> I support the initiative
>
> Lgtm
>
>
> Thanks
> Enrico
>
> Enrico
>
> Il Dom 3 Mar 2024, 04:09 Matteo Merli ha scritto:
>
> > PIP PR: https://github.com/apache/pulsar/pull/22178
> >
> > WIP of proposed implementation:
> >
I support
Pulsar is a very complex software, structuring this knowledge will be very
helpful
Kiryl Valkovich 于2024年3月2日 周六22:01写道：
> Imagine that you are a Pulsar user or interested in data streaming in
> general and would like to contribute to some related open-source project.
> You have some
sounds great!
+1 nonbinding
Zixuan Liu 于2024年2月21日 周三13:08写道：
> Hi Pulsar Community,
>
> The pulsar CLI(pulsar-admin, pulsar-client, pulsar-shell, and so on) uses
> the jcommander [1] as CLI parser, which is an awesome project, but the
> maintainer is not active and cannot keep up with modern
congrats!
Lari Hotari 于2024年2月21日 周三00:50写道：
> The Apache Pulsar Project Management Committee (PMC) has invited
> Asaf Mesika https://github.com/asafm to become a committer and we
> are pleased to announce that he has accepted.
>
> Welcome and Congratulations, Asaf Mesika!
>
> Please join us in
+1 nonbinding
Matteo Merli 于2024年2月6日 周二04:40写道：
> https://github.com/apache/pulsar/pull/22009
>
> -
>
> # PIP-335: Support Oxia metadata store plugin
>
> # Motivation
>
> Oxia is a scalable metadata store and coordination system that can be used
> as the core infrastructure
> to
+1
Matteo Merli 于2024年2月1日 周四07:58写道：
> https://github.com/apache/pulsar/pull/22009
>
> ===
>
> # PIP-335: Supporty Oxia metadata store plugin
>
> # Motivation
>
> Oxia is a scalable metadata store and coordination system that can be used
> as the core infrastructure
> to build large
Oxia is a project of StreamNative inc, it's non public. From my
understanding, it's a zookeeper proxy, like Apache ShardingSphere, for the
purpose of zookeeper's horizontal expansion.
Dave Fisher 于2024年1月23日 周二05:23写道：
> Hi Paul,
>
> There is no such thing as Apache Oxia. It is from a vendor in
+1 nonbinding
> 2024年1月17日 17:35，Asaf Mesika 写道：
>
> +1 (non-binding)
>
> On Tue, Jan 16, 2024 at 4:43 AM Dezhi Liu wrote:
>
>> +1 (non-binding)
>>
>> Thanks,
>> Dezhi Liu
>>
>> On 2024/01/15 09:33:48 Zixuan Liu wrote:
>>> Hi Pulsar Community,
>>>
>>> Voting for PIP-330: getMessagesById
+1 nonbinding
Umut Bilal Okur 于2023年12月23日 周六00:13写道：
> +1 (non-binding)
>
> Enrico Olivelli , 22 Ara 2023 Cum, 18:26 tarihinde
> şunu yazdı:
>
> > +1 (binding)
> >
> > Enrico
> >
> > Il giorno ven 22 dic 2023 alle ore 02:46 Apurva Telang
> > ha scritto:
> > >
> > > +1 (non-binding)
> > >
> > >
Sorry, the PIP had approved, please ignore.
Tao Jiuming 于2023年12月21日周四 04:25写道：
>
> bump
>
> On 2022/11/28 08:47:01 Jiuming Tao wrote:
> > Dear Pulsar Community,
> >
> > Please review and vote on this PIP.
> >
> > PIP link: https://github.com/apache/pulsar/issues/18560
> >
> > Discuss thread:
>
In my understanding, the PIP is for some certain `extreme` conditions. Some
ledgers failing to recover is an event with a very low probability, and it
should be hard to reproduce(unless we delete some ledgers manually).
If we skip these failed-recover ledgers, message production should be able
to
congrats！
Lari Hotari 于2023年11月27日 周一19:46写道：
> Congratulations on becoming a PMC member, Daniel! Well deserved!
>
> -Lari
>
> On 2023/11/27 08:12:15 tison wrote:
> > The Apache Pulsar Project Management Committee (PMC) has invited
> > Daniel Blankensteiner https://github.com/blankensteiner to
+1 non binding
Zili Chen 于2023年11月17日 周五17:56写道：
> +1 binding
>
> Thanks for your proposal.
>
> On 2023/11/15 03:39:42 Pengcheng Jiang wrote:
> > Hi Pulsar Community,
> >
> > This thread is to start a vote for PIP-312: Use StateStoreProvider to
> > manage state in Pulsar Functions endpoints.
> >
In the past, threads usually blocked on LockUtil.park(…), and AQS is
depends on it to park threads.
Virtual thread only solved thread blocking on JDK layer by rewriting
LockUtik.park(…)
In some conditions, the carrier thread will be blocked (I only remember the
following points)
1. JNI calling
Hi Girish,
There is also a discussion thread[1] about rate-limiting.
I think there is some conflicts between some kind of rate-limiter and
backpressure
Take the fail-fast strategy as an example:
Brokers have to reply to clients after receiving and decode the message,
but the broker also has the
+1 non binding
Thanks,
Tao Jiuming
Rajan Dhabalia 于2023年10月27日 周五07:00写道：
> Thanks for adding it.
> +1
>
> Thanks,
> Rajan
>
> On Thu, Oct 26, 2023 at 3:52 PM vineeth p
> wrote:
>
> > Broker metrics don't have anything to indicate the health of the broker
> (to
> > indicate if the broker is
+1(no-binding)
Thanks,
Tao Jiuming
Cong Zhao 于2023年10月24日 周二16:03写道：
> +1(no-binding)
>
> Thanks,
> Cong Zhao
>
> On 2023/10/19 12:47:45 guo jiwei wrote:
> > Hi dev,
> >Currently WebSocket only supports the consumption of a single topic,
> > which cannot satisfy users' consumption scenarios
+1 (no-binding)
Zixuan Liu 于2023年9月26日 周二10:54写道：
> Hi Pulsar Community,
>
> Voting for PIP-300: https://github.com/apache/pulsar/pull/21127
> Discussion thread:
> https://lists.apache.org/thread/ysnsnollgy1b6w1dsvmx1t1y2rz1tyd6
>
> Thanks,
> Zixuan
>
+1 (no-binding)
Xiangying Meng 于2023年9月27日 周三15:05写道：
> Hi dev,
>This thread is to start a vote for PIP-302 Add new API
> refreshAsync for TableView.
> Discuss thread:
> https://lists.apache.org/thread/o085y2314o0fymvx0x8pojmgjwcwn59q
> PIP: https://github.com/apache/pulsar/pull/21166
>
>
+1 non-binding
Thanks,
Tao Jiuming
Zixuan Liu 于2023年8月5日 周六22:58写道：
> +1 (non-binding)
>
> Thanks,
> Zixuan
>
> 于2023年8月5日周六 21:11写道：
> >
> > +1 (binding)
> >
> > Best,
> > Mattison
> > On 5 Aug 2023 at 20:05 +0800, Yunze Xu , wrote:
> > > +1 (binding)
> > >
> > > Thanks,
> > > Yunze
> > >
> >
+1
Thanks,
Tao Jiuming
Yunze Xu 于2023年7月31日 周一16:26写道：
> LGTM.
>
> Thanks,
> Yunze
>
> On Wed, Jul 26, 2023 at 5:11 PM tison wrote:
> >
> > Hi,
> >
> > ## Motivation
> >
> > Pulsar brokers serve two kinds of client-side requests: data panel
> requests
> > (often known as client-api) and
Congrats!!
Thanks,
Tao Jiuming
> 2023年3月29日 23:51，Devin Bost 写道：
>
> Congrats!
>
> Devin G. Bost
>
>
> On Wed, Mar 29, 2023 at 6:38 AM ZhangJian He wrote:
>
>> Congratulations!
>>
>> Thanks
>> ZhangJian He
>>
>>
>> On Wed, 29 Mar 2023 at 19:33, Haiting Jiang
>> wrote:
>>
>>>
> Perhaps clarify, they can call:
> getStats(subscriptionBacklogSize=true, getPreciseBacklog=false,
> getEarliestTimeInBacklog=false)
> Each subscription will contain backlogSize.
> The subscription with max backlogSize will also be the one with oldest
age.
Yes, "The subscription with max
he age.
>
> I would add before:
>
> > slowestReaderTimeBasedBacklogQuotaCheck
> > <
> https://github.com/apache/pulsar/blob/master/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/persistent/PersistentTopic.java#L2817>
> is
> > a totally in-memory method
Hi all,
The thread is to start the vote for PIP-248
Discussion thread:
https://lists.apache.org/thread/m7khb49pk7vdx5yxvhzhkbo7t48d0rzs
PIP link: https://github.com/apache/pulsar/issues/19601
Thanks,
Tao Jiuming
I think yes, to avoid missing something, you can take a look if you have
time.
Thanks,
Tao Jiuming
Asaf Mesika 于2023年3月9日周四 17:40写道：
> Is the PIP updated with all comments?
>
> On Thu, Mar 9, 2023 at 8:59 AM 太上玄元道君 wrote:
>
> > > backlogQuotaLimitSize
> > > sh
<
> https://github.com/apache/pulsar/blob/master/pulsar-client-admin-api/src/main/java/org/apache/pulsar/client/admin/Topics.java#L1139>
> to
> >get the topic stats, and find which subscriptions are in backlog.
> >Pulsar exposed backlogSize and earliestMsgPublishTi
Hi Aasf,
I've updated the PIP, PTAL
Thanks,
Tao Jiuming
Asaf Mesika 于2023年3月5日周日 21:00写道：
> On Thu, Mar 2, 2023 at 12:57 PM 太上玄元道君 wrote:
>
> > > I think you should fix this explanation:
> >
> > Thanks! I would like to copy the context you provide to the
in terms of I/O is limited.
> Now you are adding one additional I/O per collection, every 1 min by
> default. That's a lot perhaps. How long is the check interval today?
>
> Perhaps in the backlog quota check, you can persist the check result, and
> use it? Persist the age th
congrats!
Thanks,
Tao Jiuming
Nozomi Kurihara 于2023年2月27日周一 15:47写道：
> Hi everyone,
>
> The Project Management Committee (PMC) for Apache Pulsar
> has invited Yuri Mizushima (https://github.com/equanz) to become a
> committer and we are pleased
> to announce that he has accepted.
>
> Yuri has
Hi Rajan,
Even we don't persistent NonPersistentSubscription's state, but it has a
`isDurable` field
```
public NonPersistentSubscription(NonPersistentTopic topic, String
subscriptionName, boolean isDurable,
Map properties) {
this.topic = topic;
Hi all,
I've started a PIP to discuss: PIP-248 Add backlog eviction metric
### Motivation:
Pulsar has 2 configurations for the backlog eviction:
`backlogQuotaDefaultLimitBytes` and `backlogQuotaDefaultLimitSecond`, if
topic backlog reaches the threshold of any item, backlog eviction will be
66 matches
Mail list logo
