Re: [DISCUSSION] PIP-130: Apply redelivery backoff policy for ack timeout

2021-12-27 Thread Enrico Olivelli
Penghui I am overall +1 to this proposal but I am afraid about compatibility. Amd I won't to be sure that we are not breaking anything. Pulsar client and Consumer are configurable using a map of key value pairs. So we must take care of not changing the behaviour. What do you mean with 'redelivery

Re: [DISCUSSION] Produce chunk messages failed when topic level maxMessageSize is set

2021-12-27 Thread Enrico Olivelli
It looks loke you already prepared a awesome PIP! Please copy your proposal on a PIP. I am +1 Enrico Il Mar 28 Dic 2021, 04:27 Zike Yang ha scritto: > + 1 for skipping the topic level message size check for the chunk message > in the broker. > > On Tue, Dec 28, 2021 at 9:14 AM guo jiwei wrote

Re: [DISCUSSION] Produce chunk messages failed when topic level maxMessageSize is set

2021-12-27 Thread Zike Yang
+ 1 for skipping the topic level message size check for the chunk message in the broker. On Tue, Dec 28, 2021 at 9:14 AM guo jiwei wrote: > +1 > > > Regards > Jiwei Guo (Tboy) > > On Tue, Dec 28, 2021 at 5:44 AM 陳智弘 wrote: > > > > +1 > > > > Skip the topic level setting is better > > > > Hang

Re: [DISCUSS] Release Pulsar 2.7.4

2021-12-27 Thread guo jiwei
Hi Shivji, The 2.7.4 has been already released and includes 2.17.0. Regards Jiwei Guo (Tboy) On Tue, Dec 21, 2021 at 6:47 PM Shivji Kumar Jha wrote: > > Hi Pulsar Team, > > 2.16.0 is prone to DDoS attacks [1]. Is it possible to move to 2.17.0 in > pulsar 2.7.4 ? > > [1] https://cve.mitre.or

Re: [DISCUSSION] Produce chunk messages failed when topic level maxMessageSize is set

2021-12-27 Thread guo jiwei
+1 Regards Jiwei Guo (Tboy) On Tue, Dec 28, 2021 at 5:44 AM 陳智弘 wrote: > > +1 > > Skip the topic level setting is better > > Hang Chen 於 2021年12月27日 週一 22:09 寫道： > > > +1 > > > > We'd better skip the topic level maxMessageSize check for chunk messages. > > > > Best, > > Hang > > > > PengHui L

Re: [DISCUSSION] Produce chunk messages failed when topic level maxMessageSize is set

2021-12-27 Thread 陳智弘
+1 Skip the topic level setting is better Hang Chen 於 2021年12月27日 週一 22:09 寫道： > +1 > > We'd better skip the topic level maxMessageSize check for chunk messages. > > Best, > Hang > > PengHui Li 于2021年12月27日周一 22:07写道： > > > > +1, > > > > We can only skip the topic level messages size check fo

[ANNOUNCE] Apache Pulsar 2.7.4 released

2021-12-27 Thread guo jiwei
The Apache Pulsar team is proud to announce Apache Pulsar version 2.7.4. 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

Re: [DISCUSSION] Produce chunk messages failed when topic level maxMessageSize is set

2021-12-27 Thread Hang Chen
+1 We'd better skip the topic level maxMessageSize check for chunk messages. Best, Hang PengHui Li 于2021年12月27日周一 22:07写道： > > +1, > > We can only skip the topic level messages size check for the chunk message. > > Regards, > Penghui > > On Mon, Dec 20, 2021 at 3:37 PM Haiting Jiang > wrote: >

Re: [DISCUSSION] Produce chunk messages failed when topic level maxMessageSize is set

2021-12-27 Thread PengHui Li
+1, We can only skip the topic level messages size check for the chunk message. Regards, Penghui On Mon, Dec 20, 2021 at 3:37 PM Haiting Jiang wrote: > Hi Pulsar Community, > > I discovered a bug that chunk messages producing fails if topic level > maxMessageSize is set [1]. The root cause of

[DISCUSSION] PIP-130: Apply redelivery backoff policy for ack timeout

2021-12-27 Thread PengHui Li
https://github.com/apache/pulsar/issues/13528 Pasted below for quoting convenience. - PIP 130: Apply redelivery backoff policy for ack timeout ## Motivation PIP 106 https://github.com/apache/pulsar/wiki/PIP-106%3A-Negative-acknowledgment-backoff introduced negative acknowledgment message r