[transactions] Add admin API to abort forcibly a transaction
- Dominant language
- Java
- Stars
- 15.3k
- Forks
- 3.8k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 160
Description
### Search before asking
- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.
### Motivation
If you have a pending stuck transaction the Consumers are stuck, they cannot read beyond the beginning of the transaction.
You have to wait for the transaction timeout in order to see the system recover
### Solution
In Kafka you have ad admin command "abortTransactions", we need something like that.
https://cwiki.apache.org/confluence/display/KAFKA/KIP-664%3A+Provide+tooling+to+detect+and+abort+hanging+transactions
### Alternatives
_No response_
### Anything else?
_No response_
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
Contributor guide
Research direction
No Pulsar files, tests, or entry points are named. Start by reviewing the requested admin API alongside Kafka's abortTransactions and KIP-664; done would require an agreed API and defined behavior for forcibly aborting pending transactions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100