apache / apache/doris-flink-connector
[Bug] failed abort txn, with illegal input
- Dominant language
- Java
- Stars
- 385
- Forks
- 279
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 6
Description
### Search before asking
- [x] I had searched in the [issues](https://github.com/apache/incubator-doris/issues?q=is%3Aissue) and found no similar issues.
### Version
flink-doris-connector-1.20-25.1.0
### What's Wrong?
My Flink task had been running for two days when it suddenly reported the following exception.
Caused by: org.apache.doris.flink.exception.DorisException: Fail to abort transaction, { "status": "INTERNAL_ERROR", "msg": "failed abort txn, with illegal input, db_id=-1 txn_id=-1 label= txn_2pc_op=abort" } at org.apache.doris.flink.sink.writer.DorisStreamLoad.abortTransaction(DorisStreamLoad.java:484) ~[flink-doris-connector-1.20-25.1.0.jar:25.1.0]
### What You Expected?
No error reported.
### How to Reproduce?
_No response_
### Anything Else?
_No response_
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
Contributor guide
Research direction
Start at flink-doris-connector's DorisStreamLoad.abortTransaction method at DorisStreamLoad.java:484 and inspect how the abort request receives db_id, txn_id, and label. The report provides no reproduction steps or tests, so first determine the failure path from the stack trace and identify the conditions producing the illegal input. Done should mean the reported abort failure no longer occurs and the behavior is covered by an appropriate regression check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100