Hi, Ruihong Thanks for your proposal. I wonder whether we should abort all the transactions one client creates when the client crushes. For example, a process builds a Pulsar client and creates a transaction by this client to do some operations. If the process crushes, the transaction cannot be committed or aborted.
In this case, aborting the transaction automatically when the client is crushed may be more helpful than aborting them after restarting. BR, Xiangying On Mon, Dec 18, 2023 at 9:08 AM PengHui Li <peng...@apache.org> wrote: > Hi, Ruihong > > The proposal looks good to me. > Just left a comment about the security considerations. > We need to have a clear permission definition for newly added admin API > > Regards, > Penghui > > On Sun, Dec 17, 2023 at 1:14 AM |海阔天高 <1373544...@qq.com.invalid> wrote: > > > Hi community, > > > > > > PIP-325 introduces a new API for aborting transactions, allowing > > administrators to proactively abort a transaction when it gets stuck, > thus > > preventing consumers from being blocked for an extended period. > > > > > > Hopes for discuss. > > PIP: https://github.com/apache/pulsar/pull/21731 > > Releted PR: https://github.com/apache/pulsar/pull/21630 > > > > > > Thanks, > > > > > > Ruihong > > > > > > |海阔天高 > > 1373544...@qq.com > > > > > > > > >
