yixiutt opened a new pull request, #10007: URL: https://github.com/apache/incubator-doris/pull/10007
in concurrent stream load, fe will run publish version task concurrently, which cause publish task disorder in be. For example: fe publish task with version 1 2 3 4 be may handle task with sequence 1 2 4 3 In case above, when report tablet info, be found that version 4 published but version 3 not visable, it'll report version miss to fe, and fe will set replica lastFailedVersion, and finally makes transaction commits fail while no quorum health replicas。 Add a strategy to handle this case, be must publish version in sequence, if publish task version not match tablet max_version, it will be push back to queue and wait. # Proposed changes Issue Number: close #xxx ## Problem Summary: Describe the overview of 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/No) ## Further comments If this is a relatively large or complex change, kick off the discussion at [d...@doris.apache.org](mailto:d...@doris.apache.org) 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: commits-unsubscr...@doris.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org For additional commands, e-mail: commits-h...@doris.apache.org
