Re: [DISCUSS] PIP-240 A new API to unload subscriptions

2023-01-17 Thread PengHui Li
> What kind of problems is this trying to fix? And why cannot that be solved by client-side fixes? Yes, most of the issue is from the client side, rarely from the broker. But the application also needs time to fix the issue to release and deploy the fix to the production environment. Unloading the

Re: [DISCUSS] PIP-240 A new API to unload subscriptions

2023-01-17 Thread Joe F
Inclined to agree with Enrico. If it's a hard problem, it will repeat, and this is not helping. If it's some race on the client, it will occur randomly and rarely, and this unload sub will get programmed in as a way of life. >If you don't think unloading the subscription can't help anything. Unl

Re: [DISCUSS] PIP-240 A new API to unload subscriptions

2023-01-17 Thread PengHui Li
I agree that if we encounter a stuck consumption issue, we should continue to find the root cause of the problem. Subscription unloading is just an option to mitigate the impact first. Maybe it can mitigate the issue for 1 hour sometimes. Especially in key_shared subscription. Sometimes it's not a

Re: [DISCUSS] KeyShared routing additions/configuration

2023-01-17 Thread Tim Corbett
To start, sorry if this breaks threading and/or ends up looking hideous, I am new to using these mailing lists and was not subscribed so can't seem to resume the thread from the latest message. > > The proposal is two-fold: first, we would like to implement a new KeyShared > > routing mechanism wh

Re: [DISCUSS] PIP-240 A new API to unload subscriptions

2023-01-17 Thread Enrico Olivelli
Il giorno lun 16 gen 2023 alle ore 11:58 r...@apache.org ha scritto: > > I agree with @Enrico @Bo, if we encounter a subscribe stuck situation, we > must continue to spend more time to locate and fix this problem, which is > what we have been doing. > > But let's think about this problem from anot

Re: [DISCUSS] PIP-236: Upload AUTO_CONSUME SchemaType to Broker

2023-01-17 Thread SiNan Liu
The value of enum has been updated in the PIP issue . Thanks, Sinan Yunze Xu 于2023年1月17日周二 12:11写道: > > Maybe 100 or something. > > I see the updated PR adopts this suggestion to set the enum value with > 100. But I'm still wondering why not just u

Re: [DISCUSS] Make the default value of param "--get-subscription-backlog-size" of admin API "topics stats" true

2023-01-17 Thread Yubiao Feng
Hi Asaf > It's worth noting that the estimated backlog size of a subscription is estimated since it doesn't consider any acknowledged messages between the mark delete position and the last message. It simply assumes all messages between the mark delete position and the last message have not been a