为了更快的定位您的问题，请提供以下信息，谢谢
【详述】问题详细描述
【背景】做过哪些操作？
【业务影响】
【是否存算分离】
【StarRocks版本】例如：2.5.2
【集群规模】例如：3fe（3 follower+2observer）+5be（fe与be混部）
【机器信息】CPU虚拟核/内存/网卡，例如：48C/128G/万兆
【表模型】例如：主键模型
【导入或者导出方式】例如：datax
【联系方式】为了在解决问题过程中能及时联系到您获取一些日志信息，请补充下您的联系方式，例如：社区群4-小李或者邮箱，谢谢
2023-11-20 11:33:07,240 WARN (replayer|91) [GlobalStateMgr.replayJournalInner():1932] replay journal cost too much time: 1001 replayedJournalId: 33420233
2023-11-20 11:33:07,240 WARN (replayer|91) [GlobalStateMgr$5.setCanRead():1801] meta out of date. current time: 1700451187240, synchronized time: 1693126274768, has log: true, fe type: OBSERVER
2023-11-20 11:33:08,246 WARN (replayer|91) [GlobalStateMgr.replayJournalInner():1932] replay journal cost too much time: 1001 replayedJournalId: 33428007
2023-11-20 11:33:09,249 WARN (replayer|91) [GlobalStateMgr.replayJournalInner():1932] replay journal cost too much time: 1001 replayedJournalId: 33437850
2023-11-20 11:33:10,253 WARN (replayer|91) [GlobalStateMgr.replayJournalInner():1932] replay journal cost too much time: 1001 replayedJournalId: 33453558
2023-11-20 11:33:11,256 WARN (replayer|91) [GlobalStateMgr.replayJournalInner():1932] replay journal cost too much time: 1001 replayedJournalId: 33464162
2023-11-20 11:33:12,315 WARN (replayer|91) [GlobalStateMgr.replayJournalInner():1932] replay journal cost too much time: 1057 replayedJournalId: 33467047
exec plan fragment failed, errmsg=get_applied_rowsets(version 1962615) failed tablet:10032 #version:137 [5064299.1 5064434.1@136 5064434.1] #pending:0, code: NOT_FOUND, fragmentId=F01, backend=xxx.xxx.xxx:9060
2023-11-20 11:33:20,933 WARN (ForkJoinPool.commonPool-worker-88|116) [Coordinator.deliverExecBatchFragmentsRequests():1228] exec plan fragment failed, errmsg=get_applied_rowsets(version 1962615) failed tablet:10032 #version:137 [5064299.1 5064434.1@136 5064434.1] #pending:0, code: NOT_FOUND, fragmentId=F01, backend=xxx.xxx.xxx:9060
重启后还是会出现 be overladed with pipeline的错误