zhannngchen opened a new pull request, #15289:
URL: https://github.com/apache/doris/pull/15289
…
In the following case, data inconsistency would happen between multiple
replicas
current delta writer only writes a few lines of data (which meas the write()
method only called once) writer failed when init()(which is called at the fist
time we call write()), and current tablet is recorded in _broken_tablets delta
writer closed, and in the close() method, delta writer found it's not inited,
treat such case as an empty load, it will try to init again, which would create
an empty rowset. tablet sink received the error report in rpc response, marked
the replica as failed, but since the quorum replicas are succeed, so the
following load commit operation will succeed. FE send publish version task to
each be, the one with empty rowset will publish version successfully. We got 2
replica with data and 1 empty replica.
# Proposed changes
Issue Number: close #xxx
## Problem summary
Describe your changes.
## Checklist(Required)
1. Does it affect the original behavior:
- [ ] Yes
- [ ] No
- [ ] I don't know
2. Has unit tests been added:
- [ ] Yes
- [ ] No
- [ ] No Need
3. Has document been added or modified:
- [ ] Yes
- [ ] No
- [ ] No Need
4. Does it need to update dependencies:
- [ ] Yes
- [ ] No
5. Are there any changes that cannot be rolled back:
- [ ] Yes (If Yes, please explain WHY)
- [ ] No
## Further comments
If this is a relatively large or complex change, kick off the discussion at
[[email protected]](mailto:[email protected]) by explaining why you
chose the solution you did and what alternatives you considered, etc...
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
