apache
[enhance](cooldown) turn write cooldown meta async
Proposed changes
Issue Number: close #xxx Upload meta file first once this replica is chosen to be new cooldown replica. Consider such case: replica A: term 15, replica B: term 14, replica C: term 15 and the former cooldown replica is A if FE chooses C to be the new cooldown replica, and B tries to follow C now, B wouldn't be able to find .meta file on remote storage
Problem summary
Describe your changes.
Checklist(Required)
- [ ] Does it affect the original behavior
- [ ] Has unit tests been added
- [ ] Has document been added or modified
- [ ] Does it need to update dependencies
- [ ] Is this PR support rollback (If NO, please explain WHY)
Further comments
If this is a relatively large or complex change, kick off the discussion at [email protected] by explaining why you chose the solution you did and what alternatives you considered, etc...
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
TeamCity pipeline, clickbench performance test result: the sum of best hot time: 34.65 seconds stream load tsv: 472 seconds loaded 74807831229 Bytes, about 151 MB/s stream load json: 37 seconds loaded 2358488459 Bytes, about 60 MB/s stream load orc: 76 seconds loaded 1101869774 Bytes, about 13 MB/s stream load parquet: 31 seconds loaded 861443392 Bytes, about 26 MB/s https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230307182003_clickbench_pr_110297.html
