Re: [VOTE] PIP-429: Optimize Handling of Compacted Last Entry by Skipping Payload Buffer Parsing

2025-07-13 Thread Yubiao Feng
+1 binding Thanks Yubiao Feng On Sun, Jul 6, 2025 at 5:31 PM Yunze Xu wrote: > Hi all, > > I'd like to start the vote for PIP-429: Optimize Handling of Compacted > Last Entry by Skipping Payload Buffer Parsing. > > - Discussion thread: > https

Re: [Discussion] PR #24423 Handling Overloaded Netty Channels in Apache Pulsar

2025-07-13 Thread Yubiao Feng
be cherry-picked into branch-3.3 and branch-4.0. BTW, the feature `ServerCnxThrottleTracker` has a bug that the rate limiter and the mechanism named max pending publishing bytes will affect each other. I will fix the issue in the second PR as well. On Tue, Jul 8, 2025 at 2:07 PM Yubiao Feng wrote:

Re: [Discussion] PR #24423 Handling Overloaded Netty Channels in Apache Pulsar

2025-07-10 Thread Yubiao Feng
ight requests, such as > producer throttling and consumer throttling. > > Memory layer restrictions: Memory pool limitations, blocking new request > processing rather than allocating more memory when the pool is exhausted. > > On 2025/07/08 06:07:10 Yubiao Feng wrote: > > Hi al

Re: [VOTE] PIP-432: Add isEncrypted field to EncryptionContext

2025-07-10 Thread Yubiao Feng
+1 binding Thanks Yubiao Feng On Thu, Jul 10, 2025 at 10:45 PM PengHui Li wrote: > Hi Team, > > This is the official VOTE thread for PIP-432. > - Discuss thread: > https://lists.apache.org/thread/sfcc902hwlgwg21ttwkrsyx3ogt8hzon > - Proposal link: > > https://githu

Re: [Discussion] PR #24423 Handling Overloaded Netty Channels in Apache Pulsar

2025-07-10 Thread Yubiao Feng
. The purpose of the fix is not to avoid the channel being marked `not writable`, its purpose is to avoid too much memory usage because of a non-writable Netty channel. On Thu, Jul 10, 2025 at 4:54 PM Lari Hotari wrote: > On Thu, 10 Jul 2025 at 05:47, Yubiao Feng > wrote: > > Highlig

[Vote] PIP-433: Optimize the conflicts of the replication and automatic creation mechanisms, including the automatic creation of topics and schemas

2025-07-09 Thread Yubiao Feng
/p16gwhfx6rkxdp8dm9pckn43o5875o1s The vote will stay open for at least 48 hours. Thanks Yubiao Feng -- This email and any attachments are intended solely for the recipient(s) named above and may contain confidential, privileged, or proprietary information. If you are not the intended recipient, you are

Re: [Discussion] PR #24423 Handling Overloaded Netty Channels in Apache Pulsar

2025-07-09 Thread Yubiao Feng
ig will only increase the number of active packet losses and packet retransmissions of TCP, which is of no benefit to the system. It merely shifts the memory pressure to the system kernel, the implementer of the TCP protocol On Tue, Jul 8, 2025 at 2:07 PM Yubiao Feng wrote: > Hi all > > I wa

Re: [Discussion] PR #24423 Handling Overloaded Netty Channels in Apache Pulsar

2025-07-09 Thread Yubiao Feng
read should be > handled with org.apache.pulsar.broker.service.ServerCnxThrottleTracker's > incrementThrottleCount/decrementThrottleCount instead of toggling > autoread directly. (The javadoc for ServerCnxThrottleTracker contains > more details.) > > I hope this helps us find a

Re: [VOTE] PIP-420: Provide ability for Pulsar clients to integrate with third-party schema registry service

2025-07-09 Thread Yubiao Feng
+1 (binding) Thanks Yubiao Feng On Mon, Jul 7, 2025 at 10:51 AM ran leon wrote: > [VOTE] PIP-420: Provide ability for Pulsar clients to integrate with > third-party schema registry service > Hi Team, > > This is the official VOTE thread for PIP-420. > - Proposal link: https:/

[Discussion] PR #24423 Handling Overloaded Netty Channels in Apache Pulsar

2025-07-07 Thread Yubiao Feng
tly handles overload scenarios at a fundamental network layer. I invite the community to discuss this solution and its potential benefits for the overall stability and resilience of Apache Pulsar. Thanks Yubiao Feng -- This email and any attachments are intended solely for the recipient(s

Re: [DISCUSS] Cherry-pick PIP-370 configurable remote topic creation in geo-replication

2025-07-07 Thread Yubiao Feng
Hi Lari Cherry-picked into branch-3.3 Thanks Yubiao Feng On Mon, Aug 26, 2024 at 10:27 AM Yubiao Feng wrote: > Hi all > > I would like to start a discussion to cherry-pick PIP-370 into `branch-3.0` > > This PIP is very useful for the scenario of managing topics manually,

[DISCUSS] PIP-433: Optimize the conflicts of the replication and automatic creation mechanisms, including the automatic creation of topics and schemas

2025-07-03 Thread Yubiao Feng
Hi all I drafted a proposal to optimize the conflicts of the replication and automatic creation mechanisms, including the automatic creation of topics and schemas https://github.com/apache/pulsar/pull/24485 I'm looking forward to hearing from you. Thanks Yubiao Feng -- This email an

Re: [VOTE] PIP-431: Add Creation and Last Publish Timestamps to Topic Stats

2025-07-02 Thread Yubiao Feng
+1 (binding) Thanks Yubiao Feng On Wed, Jul 2, 2025 at 12:21 AM PengHui Li wrote: > Hi Team, > > This is the official VOTE thread for PIP-431. > - Discuss thread: > https://lists.apache.org/thread/mmn3hqrgn5rztdbo78prpqkc5mt3sr26 > - Proposal link: https://github.com/apache

Re: [VOTE] PIP-421: Require Java 17 as the minimum for Pulsar Java client SDK

2025-07-02 Thread Yubiao Feng
+1 (binding) Thanks Yubiao Feng On Fri, Jun 20, 2025 at 3:38 AM Matteo Merli wrote: > https://github.com/apache/pulsar/pull/24364 > > --- > > # PIP-421: Require Java 17 as the minimum for Pulsar Java client SDK > > # Context > > Currently, Pulsar requires Java 17 for

Re: [VOTE] PIP-427: Align 'set-persistence' default for mark-delete rate with broker config

2025-06-25 Thread Yubiao Feng
+1 (binding) Thanks Yubiao Feng On Sat, Jun 21, 2025 at 3:40 AM PengHui Li wrote: > Hi all, > > This is the official VOTE thread for PIP-427 > > - Discuss thread: > https://lists.apache.org/thread/j9vx6zkkgnz08sfgp14swylb8wv6djzs > - Proposal link: https://github.com/apa

Re: [DISCUSS] PIP-427: Align 'set-persistence' default for mark-delete rate with broker config

2025-06-17 Thread Yubiao Feng
It is very meaningful. Thanks Yubiao Feng On Wed, Jun 18, 2025 at 10:52 AM PengHui Li wrote: > Hi everyone, > > I would like to start a discussion on a proposal to improve the default > behavior of the pulsar-admin namespaces set-persistence command. > > *The Problem:* &g

Re: [VOTE] PIP-422 Support global topic-level policy: replicated clusters and new API to delete topic-level policies

2025-06-17 Thread Yubiao Feng
Close the vote with 3 bindings - Penghui Li(binding) - Jiwei Guo (binding), who approved the PR of the PIP https://github.com/apache/pulsar/pull/24368 - Baodi Shi (binding) Thanks Yubiao Feng On Thu, Jun 5, 2025 at 12:23 PM Yubiao Feng wrote: > Hi all > > I want to start a vote o

[VOTE] PIP-422 Support global topic-level policy: replicated clusters and new API to delete topic-level policies

2025-06-04 Thread Yubiao Feng
stay open for at least 48 hours. Thanks Yubiao Feng -- This email and any attachments are intended solely for the recipient(s) named above and may contain confidential, privileged, or proprietary information. If you are not the intended recipient, you are hereby notified that any disclosure

[DISCUSS] PIP-422 Support global topic-level policy: replicated clusters and new API to delete topic-level policies

2025-05-30 Thread Yubiao Feng
`, `branch-3.3` and `branch-4.0` after it finished I'm looking forward to hearing from you. Thanks Yubiao Feng -- This email and any attachments are intended solely for the recipient(s) named above and may contain confidential, privileged, or proprietary information. If you are not the int

Re: [DISCUSS] PIP-387: Modify interface TopicCompactionService to support cancelling an in-progress compaction task

2025-05-28 Thread Yubiao Feng
Hi all I cancelled this proposal On Wed, Oct 16, 2024 at 1:52 AM Yubiao Feng wrote: > Hi all > > I want to start a discussion on PIP-387: Modify interface > TopicCompactionService to support canceling an in-progress compaction task > > Proposal link: https://github.com/apache

Re: [VOTE] PIP-415: Support getting message ID by offset

2025-05-19 Thread Yubiao Feng
+1 (binding) Thanks Yubiao Feng On Thu, May 8, 2025 at 10:59 AM xiangying meng wrote: > Hi, all > > I`d like to start a vote on PIP-415: Support getting message ID by offset. > > You can find the proposal at > https://github.com/apache/pulsar/pull/24220 and the discussion

Re: [DICUSS] Cherry-pick #22792 into branch-3.0 and branch-3.3

2025-05-06 Thread Yubiao Feng
Cherry-picked On Sat, Apr 26, 2025 at 4:21 PM Yubiao Feng wrote: > Hi all > > Before #22792, brokers searched messages by timestamp as follows > - Binary search entries > - Reading the entry and getting the entry's publish timestamp > > After #22792, brokers searche

Re: New PMC member: Zixuan Liu

2025-05-05 Thread Yubiao Feng
Congratulations! Zixuan Thanks Yubiao Feng On Fri, May 2, 2025 at 7:05 PM Lari Hotari wrote: > The Project Management Committee (PMC) for Apache Pulsar > is delighted to announce that Zixuan Liu has joined the PMC! > > Zixuan has been an active contributor to Apache Pulsar,

Re: [DICUSS] Cherry-pick #22792 into branch-3.0 and branch-3.3

2025-04-26 Thread Yubiao Feng
And the PR #23919, which is a fix for #22792 On Sat, Apr 26, 2025 at 4:21 PM Yubiao Feng wrote: > Hi all > > Before #22792, brokers searched messages by timestamp as follows > - Binary search entries > - Reading the entry and getting the entry's publish timestamp >

[DICUSS] Cherry-pick #22792 into branch-3.0 and branch-3.3

2025-04-26 Thread Yubiao Feng
ch between the range obtained by the first step #22792 reduces reading entries, which is very useful at the following scenarios - Consumers seek - Reset cursor - TTL - ... I would like to cherry-pick PIP-406 to branch-4.0. Thanks Yubiao Feng -- This email and any attachments are intended sole

Re: [DICUSS] Cherry-pick PIP-406 to branch-4.0

2025-03-24 Thread Yubiao Feng
+1 Thanks Yubiao Feng On Mon, Mar 24, 2025 at 9:22 AM Baodi Shi wrote: > hi, all. > > I would like cherry-pick PIP-406 to branch-4.0. > > This add new metric for the RateLimit. but doesn't introduce any > compatibility issues. I'd like to hear your thoughts. > &

Re: [VOTE] PIP-406: Introduce metrics related to dispatch throttled events

2025-03-17 Thread Yubiao Feng
+1 (binding) Thanks Yubiao Feng On Thu, Mar 13, 2025 at 9:02 PM Baodi Shi wrote: > hi, All. > > I would like to start the voting thread for PIP-406: Introduce > metrics related to dispatch throttled events > > PIP: https://github.com/apache/pulsar/pull/23945 > D

Re: [VOTE] Release Apache Pulsar 0.5.0

2025-03-03 Thread Yubiao Feng
Thanks for driving the release -1 (binding) Checks: - Download tar file ``` wget https://dist.apache.org/repos/dist/dev/pulsar/pulsar-manager/pulsar-manager-0.5.0/apache-pulsar-manager-0.5.0-bin.tar.gz ``` - Check CRC ``` 257a4f6e496106a27ade4387cf93b36e6cb7bab9e27ab199576e5f336107eff0a0fc4184f6

Re: [VOTE] PIP-409: support producer configuration for retry/dead letter topic producer

2025-02-28 Thread Yubiao Feng
+1(binding) Thanks Yubaio Feng On Thu, Feb 27, 2025 at 12:02 PM thetumbled wrote: > Hi, Pulsar Community. > I would like to start the voting thread for PIP-409: support producer > configuration for retry/dead letter topic producer. > pip link: https://github.com/apache/pulsar/pull/24022 >

Re: [DISCUSS] PIP-406: Introduce pulsar_subscription_dispatch_throttled_msgs and bytes metrics

2025-02-10 Thread Yubiao Feng
Hi Baodi I think the new subscription stats variable is useful. And I left a little comment under the PIP PR Thanks Yubiao Feng On Fri, Feb 7, 2025 at 5:31 PM Baodi Shi wrote: > I have created a PIP to introduce > pulsar_subscription_dispatch_throttled_msgs and bytes metrics > &g

Re: [DISCUSS] Add an optional config to disable the feature that compresses cursor metadata, which contributed by #9292

2025-01-24 Thread Yubiao Feng
-4.0 And I pushed a PR to set the default value of the feature to `true` to improve `branch-4.1` - https://github.com/apache/pulsar/pull/23888 On Mon, Dec 23, 2024 at 11:53 AM Yubiao Feng wrote: > Hi all > > ## Background > PR #9292 improved the serialization for cursor metadata, w

Re: [DISCUSS] Add an optional config to disable the feature that compresses cursor metadata, which contributed by #9292

2025-01-20 Thread Yubiao Feng
Hi all - To maintain compatibility, I will cherry-pick #9292 for branch-3 and branch-3.3 and cherry-pick and #23759 into branch-3., branch-3.3 and branch-4.0 after 48 hours. Please share your views if you have concerns. On Mon, Jan 20, 2025 at 9:47 AM Yubiao Feng wrote: > Hi all > >

Re: [DISCUSS] Add an optional config to disable the feature that compresses cursor metadata, which contributed by #9292

2025-01-19 Thread Yubiao Feng
Hi all Since no more arguments, I merged the PR On Tue, Jan 14, 2025 at 5:05 PM Yubiao Feng wrote: > Hi Lari > > > Let's start making progress: > > - keep PR 9292 as default > > - implement PR 23759 without changing the PR 9292 default > > - write a proper

Re: [DISCUSS] Add an optional config to disable the feature that compresses cursor metadata, which contributed by #9292

2025-01-14 Thread Yubiao Feng
ense to me, there is no discussion to announce the feature before, and users never realized it in any doc so far. Thanks Yubiao Feng On Tue, Jan 14, 2025 at 3:56 PM Lari Hotari wrote: > On Tue, 14 Jan 2025 at 09:26, Baodi Shi wrote: > > > > hi, @lari and @enrico thanks for discuss.

Re: [DISCUSS] Add an optional config to disable the feature that compresses cursor metadata, which contributed by #9292

2025-01-12 Thread Yubiao Feng
9:15 PM Lari Hotari wrote: > On Thu, 9 Jan 2025 at 14:26, Yubiao Feng > wrote: > > > Isn't the typical way to handle regressions and bugs to fix them? > > > > It may have other potential issues. > > > > > I don't see a sensible argument for changi

Re: [VOTE] PIP-399: Fix Metric Name for Delayed Queue

2025-01-10 Thread Yubiao Feng
+1 (binding) Thanks Yubiao Feng On Fri, Jan 3, 2025 at 6:08 PM thetumbled wrote: > Hi, Pulsar Community. > I would like to start the voting thread for PIP-399: Fix Metric Name for > Delayed Queue. > PIP link: https://github.com/apache/pulsar/pull/23789 > Implementat

Re: [DISCUSS] Add an optional config to disable the feature that compresses cursor metadata, which contributed by #9292

2025-01-09 Thread Yubiao Feng
? On Thu, Jan 2, 2025 at 3:25 PM Lari Hotari wrote: > On 2024/12/30 02:15:52 Yubiao Feng wrote: > > Hi Lari > > > > > I disagree on making a change to the Pulsar 4.0 default value since > > Pulsar 4.0 has already been released. > > > > Since PR #929

Re: [DISCUSS] Add an optional config to disable the feature that compresses cursor metadata, which contributed by #9292

2024-12-29 Thread Yubiao Feng
ter downgrade without > losing individual ack information. > We should have a separate upgrade guide where this is explained. > In general users will benefit of the PR-9292 behavior so there shouldn't > be a reason to postpone this for 5.0. > > -Lari > > On 2024/12/24 02:16

Re: [DISCUSS][Cherry-pick] #23757 makes replicateSubscriptionState nullable

2024-12-24 Thread Yubiao Feng
+1 Thanks Yubiao Feng On Wed, Dec 25, 2024 at 11:32 AM Dezhi Liu wrote: > +1 nonbinding > > Dezhi >

Re: [DISCUSS] Add an optional config to disable the feature that compresses cursor metadata, which contributed by #9292

2024-12-23 Thread Yubiao Feng
On Mon, Dec 23, 2024 at 01:43 Baodi Shi wrote: > > > +1 #9292 > > > > > > Thanks, > > Baodi Shi > > > > Yubiao Feng 于2024年12月23日周一 > 11:56写道: > > > > > > Hi all > > > > > > ## Background > > > PR #9292 imp

[DISCUSS] Add an optional config to disable the feature that compresses cursor metadata, which contributed by #9292

2024-12-22 Thread Yubiao Feng
Hi all ## Background PR #9292 improved the serialization for cursor metadata, which reduces Young GC and makes Pulsar persist more ack records of the cursor, but it also caused two issues below **Issue-1: Downgrade compatibility issue** - It changed the default implementation of cursor serializat

[DISCUSS] Denied creating subscriptions with special characters other than underscores and dash

2024-11-21 Thread Yubiao Feng
dashes. Highlight: the component Pulsar Function already used `/` creating subscriptions, see the test here: https://github.com/apache/pulsar/actions/runs/11801019972/job/32875168021?pr=23594 Thanks Yubiao Feng

[VOTE] PIP-394 Add two interfaces CursorMetadataSerializerProvider and CursorMetadataDeSerializerProvider to support newer of customized cursor metadata serializations

2024-11-19 Thread Yubiao Feng
/thread/xy1prwcv4wdoobphcgloj7s5gxy05qq3 The vote will stay open for at least 48 hours. Thanks Yubiao Feng

Re: [VOTE] PIP-353: PIP-392: Add configuration to enable consistent hashing to select active consumer for partitioned topic

2024-11-18 Thread Yubiao Feng
+1 (binding) Thanks Yubiao Feng On Fri, Nov 15, 2024 at 7:25 PM Baodi Shi wrote: > Hi all, > > I would like to start the voting thread for PIP-392: Add configuration > to enable consistent hashing to select active consumer for partitioned > topic > > Proposal PR: http

[DISCUSS] PIP-394 Add two interfaces CursorMetadataSerializerProvider and CursorMetadataDeSerializerProvider to support newer of customized cursor metadata serializations

2024-11-18 Thread Yubiao Feng
from you. Thanks Yubiao Feng

Re: [DISCUSS] PIP-353: PIP-392: Add configuration to enable consistent hashing to select active consumer for partitioned topic

2024-11-11 Thread Yubiao Feng
Hi Baodi Agree, I think it is useful. Thanks Yubiao Feng On Mon, Nov 11, 2024 at 4:32 PM Baodi Shi wrote: > Hi all, I push a pip to add a configuration to enable consistent > hashing to select active consumer for partitioned topic > > https://github.com/apache/pulsar/pull/2358

[DISCUSS] PIP-387: Modify interface TopicCompactionService to support cancelling an in-progress compaction task

2024-10-15 Thread Yubiao Feng
Hi all I want to start a discussion on PIP-387: Modify interface TopicCompactionService to support canceling an in-progress compaction task Proposal link: https://github.com/apache/pulsar/pull/23462 I'm looking forward to hearing from you. Thanks Yubiao Feng

[VOTE] PIP-382: Add a label named reason for topic_load_failed_total

2024-10-15 Thread Yubiao Feng
Yubiao Feng

Re: [DISCUSS] Revert the PR 23395, which broke the behavior of schemas

2024-10-10 Thread Yubiao Feng
Hi Ranjan, Lari > Until then I have created a PR to resolve this disagreement with your suggestion: > PR: https://github.com/apache/pulsar/pull/23428 Make sense. I think we can close the discussion. Thanks Yubiao Feng On Thu, Oct 10, 2024 at 4:17 AM Rajan Dhabalia wrote: > Let

Re: [DISCUSS] Revert the PR 23395, which broke the behavior of schemas

2024-10-09 Thread Yubiao Feng
ly published. If users want to remove all schemas, they can call the API that is used to remove all schemas manually. Thanks Yubiao Feng On Wed, Oct 9, 2024 at 12:51 PM Rajan Dhabalia wrote: > >> When the schemas of a topic are lost, all of the messages in the topic > can not be consume

Re: [DISCUSS] Revert the PR 23395, which broke the behavior of schemas

2024-10-09 Thread Yubiao Feng
2`, > consuming the M3(id:1 `String`) message will get an error, right? > > Thanks, > Baodi Shi > > Yubiao Feng 于2024年10月9日周三 11:29写道: > > > > Hi all > > > > Background: When the schemas of a topic are lost, all of the messages in > > the topic

[DISCUSS] Revert the PR 23395, which broke the behavior of schemas

2024-10-08 Thread Yubiao Feng
with schema `String`, get schema id `1` The messages `M1` and `M3` use different schemas, but have the same schema id, but users assume all things are fine, which is dangerous. So I want to revert this PR. Thanks Yubiao Feng

Re: [DISCUSS] GEO-replication issues on topic level

2024-10-08 Thread Yubiao Feng
cted problems. https://github.com/apache/pulsar/pull/22537 has implemented it. Thanks Yubiao Feng On Fri, Mar 22, 2024 at 4:44 PM Zixuan Liu wrote: > Hi all, > > The GEO-replication can be enabled on the Namespace and topic levels. When > GEO-replication is enabled on the namespac

Re: [DISCUSS] PIP-383: Support granting/revoking permissions for multiple topics

2024-09-28 Thread Yubiao Feng
Hi Jiwei I think it is very useful Thanks Yubiao Feng On Thu, Sep 26, 2024 at 10:06 PM guo jiwei wrote: > Hello, > > I have created a PIP for supporting granting/revoking permissions for > multiple topics. > > In AuthorizationProvider, the authorization interface >

Re: [DISCUSS] Cherry-pick PIP-370 configurable remote topic creation in geo-replication

2024-09-25 Thread Yubiao Feng
elease quickly, so I want to skip it Thanks Yubiao Feng On Wed, Sep 11, 2024 at 2:11 PM Lari Hotari wrote: > One more question about this. Why did we cherry-pick to branch-3.0, but > skip branch-3.3? > Usually we cherry-pick to all maintenance versions along the way if we do > cherr

[DISCUSS] PIP-382: Add a label named reason for topic_load_failed_total

2024-09-25 Thread Yubiao Feng
Hi all I want to start a discussion on PIP-382: Add a label named reason for topic_load_failed_total Proposal link: https://github.com/apache/pulsar/pull/23351 I'm looking forward to hearing from you. Thanks Yubiao Feng

Re: Reverting some cherry-picks in branch-3.3 and branch-3.0

2024-09-24 Thread Yubiao Feng
Hi Lari +1, thanks for your hard work Thanks Yubiao Feng On Tue, Sep 24, 2024 at 10:59 PM Lari Hotari wrote: > Hi all, > > I'm reverting 3 cherry-pick PRs in branch-3.3 and branch-3.0 due to a > performance regression: > - https://github.com/apache/pulsar/pull/23226 &g

[VOTE] PIP-375 Expose the Admin client configs: readTimeout, requestTimeout, and connectionTimeout

2024-08-27 Thread Yubiao Feng
at least 48 hours. Thanks Yubiao Feng

Re: [DISCUSS] Cherry-pick PIP-370 configurable remote topic creation in geo-replication

2024-08-27 Thread Yubiao Feng
Hi all Cherry-picked. Thanks Yubiao Feng On Mon, Aug 26, 2024 at 10:27 AM Yubiao Feng wrote: > Hi all > > I would like to start a discussion to cherry-pick PIP-370 into `branch-3.0` > > This PIP is very useful for the scenario of managing topics manually, it > provides a met

[DISCUSS] PIP-375 Expose the Admin client configs: readTimeout, requestTimeout, and connectionTimeout

2024-08-26 Thread Yubiao Feng
Hi all I drafted a proposal to expose the Admin client configs: `readTimeout`, `requestTimeout`, and `connectionTimeout` https://github.com/apache/pulsar/pull/23222 I'm looking forward to hearing from you. Thanks Yubiao Feng

Re: [DISCUSS] Cherry-pick PIP-359 Support custom message listener executor for specific subscription

2024-08-25 Thread Yubiao Feng
+1 BTW. there is a mistake in your email content: The "PIP-xxx" includes the following PRs On Mon, Aug 26, 2024 at 10:39 AM xiangying meng wrote: > Hi all > > I would like to start a discussion to cherry-pick PIP-359 into `branch-3.0` > > This PIP is very useful for scenarios where the same Cl

[DISCUSS] Cherry-pick PIP-370 configurable remote topic creation in geo-replication

2024-08-25 Thread Yubiao Feng
gracefully cherry-pick it. The PIP-370 includes the following PRs - https://github.com/apache/pulsar/pull/23169 - https://github.com/apache/pulsar/pull/23213 The thread will remain in the open state for 48 hours. If there is no objection, I will perform the cherry-picking. Thanks Yubiao Feng

Re: [DISCUSS] PIP-373: Add a topic's system prop that indicates whether users have published TXN messages in before

2024-08-23 Thread Yubiao Feng
`, and it does not contain TXN messages. Thanks Yubiao Feng On Fri, Aug 23, 2024 at 4:47 PM xiangying meng wrote: > Hi yubiao > Then return to your plan, must we set the system property to false for > topics that do not use transactions? I understand that it is enough to > only se

[VOTE] PIP-373: Add a topic's system prop that indicates whether users have published TXN messages in before

2024-08-23 Thread Yubiao Feng
will stay open for at least 48 hours. Thanks Yubiao Feng

Re: [DISCUSS] PIP-373: Add a topic's system prop that indicates whether users have published TXN messages in before

2024-08-23 Thread Yubiao Feng
t; Xiangying > > On Thu, Aug 22, 2024 at 10:53 AM Ran Gao wrote: > > > > LGTM > > > > Not all topics use the transaction feature, it can save a lot of > resources to help reduce broker recovery time, and it's convenient to > calculate topics count that use tr

[DISCUSS] PIP-373: Add a topic's system prop that indicates whether users have published TXN messages in before

2024-08-21 Thread Yubiao Feng
Hi all I drafted a proposal to add a topic's system prop that indicates whether users have published TXN messages in before. https://github.com/apache/pulsar/pull/23210 I'm looking forward to hearing from you. Thanks Yubiao Feng

Re: [VOTE] PIP-370: An optional flag: disable the replicators to automatically trigger topic creation

2024-08-15 Thread Yubiao Feng
The vote is approved with 4 binding votes and close now. Votes: - Hang Chen (binding) - Jiwei Guo (binding) - Lari Hotari (binding) - Penghui Li (binding) approved the proposal PR today, see https://github.com/apache/pulsar/pull/23124 Thank you all for voting! Thanks, Yubiao Feng On Mon, Aug

[VOTE] PIP-370: An optional flag: disable the replicators to automatically trigger topic creation

2024-08-11 Thread Yubiao Feng
open for at least 48 hours. Thanks Yubiao Feng

[DISCUSS] PIP-370: An optional flag: disable the replicators to automatically trigger topic creation

2024-08-05 Thread Yubiao Feng
Hi all I drafted a proposal to add an optional flag: disable the replicators to automatically trigger topic creation. https://github.com/apache/pulsar/pull/23124 I'm looking forward to hearing from you. Thanks Yubiao Feng

Re: [VOTE] PIP-366: Support to specify different config for Configuration and Local Metadata Store

2024-07-24 Thread Yubiao Feng
+1 (binding) Thanks Yubiao Feng On Mon, Jul 22, 2024 at 9:46 AM Kai Wang wrote: > Hi all, I want to start a vote on PIP-366: Support to specify different > config for Configuration and Local Metadata Store. > > You can find the proposal at https://github.com/apache/pulsar/pull

Re: [DISCUSS] Cherry-pick PIP-344 Correct the behavior of the public API pulsarClient.getPartitionsForTopic

2024-06-27 Thread Yubiao Feng
Cherry-picked Thanks Yubiao Feng On Fri, Jun 21, 2024 at 8:52 AM Yubiao Feng wrote: > Hi all > > Now `3.0.x` has this fix, but the newest version(`3.3.x`) doesn't contain > this fix, which is somewhat confusing, so I want to cherry-pick it to > `branch-3.3`. > > The t

Re: [DISCUSS] Cherry-pick PIP-356 Support Geo-Replication starts at earliest position

2024-06-27 Thread Yubiao Feng
Hi all > Addational: I want to cherry-pick it to `branch-3.3` too. Cherry-picked. On Fri, Jun 21, 2024 at 8:53 AM Yubiao Feng wrote: > Hi all > > Addational: I want to cherry-pick it to `branch-3.3` too. > > The thread will remain open for 48 hours. > If there is no obje

Re: [VOTE] PIP-364: Introduce a new load balance algorithm AvgShedder.

2024-06-25 Thread Yubiao Feng
+1 Thanks Yubiao Feng On Wed, Jun 26, 2024 at 11:00 AM thetumbled wrote: > Hi, Pulsar Community. > I would like to start the voting thread for PIP-364: Introduce a new > load balance algorithm AvgShedder. > Proposal PR: https://github.com/apache/pulsar/pull/22946 > Im

Re: [DISCUSS] PIP-364: Introduce a new load balance algorithm AvgShedder.

2024-06-24 Thread Yubiao Feng
> Thanks, you have done great analysis. I think it makes sense to take this forward. Agree with Lari Thanks Yubiao Feng On Thu, Jun 20, 2024 at 12:13 PM thetumbled wrote: > Hi, Pulsar Community. > I open a new PIP to introduce a new load balance algorithm AvgShedder, > which

Re: [DISCUSS] Cherry-pick PIP-356 Support Geo-Replication starts at earliest position

2024-06-20 Thread Yubiao Feng
Hi all Addational: I want to cherry-pick it to `branch-3.3` too. The thread will remain open for 48 hours. If there is no objection, I will perform the cherry-picking. Thanks Yubiao Feng On Wed, Jun 19, 2024 at 10:29 PM Yubiao Feng wrote: > Hi all > > I would like to start a disc

Re: [DISCUSS] Cherry-pick PIP-344 Correct the behavior of the public API pulsarClient.getPartitionsForTopic

2024-06-20 Thread Yubiao Feng
Hi all Now `3.0.x` has this fix, but the newest version(`3.3.x`) doesn't contain this fix, which is somewhat confusing, so I want to cherry-pick it to `branch-3.3`. The thread will remain open for 48 hours. If there is no objection, I will perform the cherry-picking. Thanks Yubiao Feng O

[DISCUSS] Cherry-pick PIP-356 Support Geo-Replication starts at earliest position

2024-06-19 Thread Yubiao Feng
target cluster. So it is very useful for the old cluster, I want to cherry-pick it into the long-term support version `3.0.x`. The thread will remain in the open state for 48 hours. If there is no objection, I will perform the cherry-picking. Thanks Yubiao Feng

Re: [VOTE] PIP-359: Support custom message listener executor for specific subscription

2024-06-19 Thread Yubiao Feng
+1 (binding) Thanks Yubiao Feng On Wed, Jun 19, 2024 at 12:45 AM Aurora Twinkle wrote: > Hi, Pulsar Community: I would like to start the voting thread for > PIP-359: Support > custom message listener executor for specific subscription. > PIP: https://github.com/apache/pulsa

Re: [DISCUSS] Cherry-pick PIP-344 Correct the behavior of the public API pulsarClient.getPartitionsForTopic

2024-06-19 Thread Yubiao Feng
Cherry-picked Thanks Yubioa Feng On Mon, Jun 17, 2024 at 11:48 PM Yubiao Feng wrote: > Hi all > > I would like to start a discussion to cherry-pick PIP-344 into `branch-3.0` > - https://github.com/apache/pulsar/pull/22206 > - https://github.com/apache/pulsar/pull/22773 > -

[DISCUSS] Cherry-pick PIP-344 Correct the behavior of the public API pulsarClient.getPartitionsForTopic

2024-06-17 Thread Yubiao Feng
cause unexpected partitioned topic creation when users call "pulsarClient.getPartitionsForTopic". So I want to cherry-pick it into the long-term support version `3.0.x` The thread will keep open for 48 hours. If there is no objections, I will perform the cherry-picking. Thanks Yubiao Feng

Re: [DISCUSS] PIP-359: Support custom message listener executor for specific subscription

2024-06-13 Thread Yubiao Feng
Same as Lari Thanks Yubiao Feng On Thu, Jun 13, 2024 at 8:05 PM Aurora Twinkle wrote: > Hi, Pulsar Community. > I open a new PIP for support custom message listener executor for specific > subscription to avoid individual subscription listener consuming too much > time leadi

Re: [VOTE] PIP-358: let resource weight work for OverloadShedder, LeastLongTermMessageRate, ModularLoadManagerImpl.

2024-06-13 Thread Yubiao Feng
+1 (binding) Thanks Yubiao Feng On Fri, Jun 14, 2024 at 10:09 AM thetumbled wrote: > Hi, Pulsar Community. >   I would like to start the voting thread for PIP-358: let resource > weight work for OverloadShedder, LeastLongTermMessageRate, > ModularLoadManagerImpl. >   Prop

Re: [DISCUSS] PIP-358: let resource weight work for OverloadShedder, LeastLongTermMessageRate, ModularLoadManagerImpl.

2024-06-12 Thread Yubiao Feng
Sounds good Thanks Yubiao Feng On Tue, Jun 11, 2024 at 11:50 AM thetumbled wrote: > Hi, Pulsar Community. > I open a new PIP for making resource weight conf work for > OverloadShedder, LeastLongTermMessageRate, ModularLoadManagerImpl, so that > we can avoid the impact of memo

Re: [VOTE] PIP-357: Correct the conf name in load balance module.

2024-06-06 Thread Yubiao Feng
+1 binding Thanks Yubiao Feng On Wed, Jun 5, 2024 at 10:33 AM thetumbled wrote: > Hi, Pulsar Community. > I would like to start the voting thread for PIP-357: Correct the conf > name in load balance module. > Proposal PR: https://github.com/apache/pulsar/pull/22823 > Im

Re: [VOTE] PIP-356: Support Geo-Replication starts at earliest position

2024-06-02 Thread Yubiao Feng
Close the vote with 3 bindings - Zike Yang(binding) - Jiwei Guo (binding) - Haiting Jiang (binding) Thanks Yubiao Feng On Thu, May 30, 2024 at 3:28 PM Yubiao Feng wrote: > Hi, all > > I would like to start the voting thread for PIP-356: Support > Geo-Replication at the earli

Re: [VOTE] PIP-355: Enhancing Broker-Level Metrics for Pulsar

2024-05-31 Thread Yubiao Feng
+1 (binding) Thanks Yubiao Feng On Fri, May 31, 2024 at 8:47 AM Hang Chen wrote: > 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 >

[VOTE] PIP-356: Support Geo-Replication starts at earliest position

2024-05-30 Thread Yubiao Feng
Hi, all I would like to start the voting thread for PIP-356: Support Geo-Replication at the earliest position. https://github.com/apache/pulsar/pull/22806 Thanks Yubiao Feng

[DISCUSS] PIP-344: Support Geo-Replication starts at earliest position

2024-05-28 Thread Yubiao Feng
Hi all I drafted a proposal to let Geo-Replication support start at the earliest position. https://github.com/apache/pulsar/pull/22791 I'm looking forward to hearing from you. Thanks Yubiao Feng

Re: [VOTE] PIP-354: apply topK mechanism to ModularLoadManagerImpl

2024-05-27 Thread Yubiao Feng
+1 (binding) Thanks Yubiao Feng On Sun, May 26, 2024 at 10:14 PM thetumbled wrote: > Hi, Pulsar Community. > I would like to start the voting thread for PIP-354: apply topK > mechanism to ModularLoadManagerImpl. > Proposal PR: https://github.com/apache/pulsar/pull/22765 >

Re: [VOTE] PIP-353: Improve transaction message visibility for peek-messages

2024-05-23 Thread Yubiao Feng
+1 (binding) Thanks Yubiao Feng On Wed, May 22, 2024 at 9:55 PM Baodi Shi wrote: > Hi, all > > I would like to start the voting thread for PIP-353. > https://github.com/apache/pulsar/pull/22746 > > The implementation PR is: > https://github.com/apache/pulsar/pull/227

Re: [DISCUSS] PIP-353: Improve transaction message visibility for peek-messages

2024-05-21 Thread Yubiao Feng
LGTM. +1 Thanks Yubiao Feng On Mon, May 20, 2024 at 6:49 PM Baodi Shi wrote: > 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 >

Re: [DISCUSS] Regarding DLQ/Retry Topic auto creation, do not create partitioned DLQ/Retry Topic

2024-05-15 Thread Yubiao Feng
Hi all The PR #22705 has been merged and I cherry-picked it into branch 3.0 Close this discussion. Thanks Yubiao Feng. On Tue, May 14, 2024 at 2:56 AM Yubiao Feng wrote: > Hi community > > I want to change the behavior of DLQ/Retry Topic auto creation. > > ### Motivation

Re: [DISCUSS] Regarding DLQ/Retry Topic auto creation, do not create partitioned DLQ/Retry Topic

2024-05-14 Thread Yubiao Feng
iption}-DLQ` We can not name the DLQ as `t1-DLQ` if the primary topic is partitioned because we can not define the behavior after users expending the partitions of `t1` to `20`. After the PR, the DLQ related to the partitions expanded will be created automatically, which is expected. Thanks Yubia

Re: [DISCUSS] Regarding DLQ/Retry Topic auto creation, do not create partitioned DLQ/Retry Topic

2024-05-13 Thread Yubiao Feng
> And I want to cherry-pick the improvement > PR into branch-3.0 The issue described above will generate much more dirty partitioned and non-partitioned topics, which should be fixed for the LTS version. Thanks Yubiao Feng On Tue, May 14, 2024 at 2:56 AM Yubiao Feng wrote: > Hi

Re: [DISCUSS] Regarding DLQ/Retry Topic auto creation, do not create partitioned DLQ/Retry Topic

2024-05-13 Thread Yubiao Feng
May 14, 2024 at 2:56 AM Yubiao Feng wrote: > Hi community > > I want to change the behavior of DLQ/Retry Topic auto creation. > > ### Motivation > After you set `defaultNumPartitions` to `16`, you will get `16` partitions > per topic, and `16*16` DLQ partitions per subscription, y

Re: [DISCUSS] Regarding DLQ/Retry Topic auto creation, do not create partitioned DLQ/Retry Topic

2024-05-13 Thread Yubiao Feng
And I want to cherry-pick the improvement PR into branch-3.0 Thanks Yubiao Feng On Tue, May 14, 2024 at 2:56 AM Yubiao Feng wrote: > Hi community > > I want to change the behavior of DLQ/Retry Topic auto creation. > > ### Motivation > After you set `defaultNumPartitions` to

[DISCUSS] Regarding DLQ/Retry Topic auto creation, do not create partitioned DLQ/Retry Topic

2024-05-13 Thread Yubiao Feng
partitioned DLQs/Retry topics automatically. - Users can also create partitioned DLQ manually if they need it. I have drafted a PR, please take a look - https://github.com/apache/pulsar/pull/22705 Thanks Yubiao Feng

Re: [VOTE] PIP-349: Add systemCursorNames ignore list for TTL check

2024-05-08 Thread Yubiao Feng
+1 (binding) Thanks Yubiao Feng On Tue, May 7, 2024 at 11:25 AM Hang Chen wrote: > 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: > https:/

Re: [VOTE] PIP-348: Trigger offload on topic load stage

2024-05-08 Thread Yubiao Feng
+1 (binding) Thanks Yubiao Feng On Tue, May 7, 2024 at 11:27 AM Hang Chen wrote: > 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: > https:/

Re: [DISCUSS] PIP-349: Add systemCursorNames ignore list for TTL check

2024-05-05 Thread Yubiao Feng
Hi Hang Agree with you. Thanks Yubiao Feng On Sun, May 5, 2024 at 12:01 AM Hang Chen wrote: > 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 >

  1   2   3   >