[Bug]: Prepare Execution Failed in Update due to file xxxx is not found

[sukki37]

Is there an existing issue for the same bug?

• I have checked the existing issues.

Branch Name

v1.0.2

Commit ID

8081e05

Other Environment Information

- Hardware parameters:
- OS type:
- Others:

Actual Behavior

http://121.43.41.174/explore?panes=%7B%22ahJ%22:%7B%22datasource%22:%22loki%22,%22queries%22:%5B%7B%22refId%22:%22A%22,%22expr%22:%22%7Bnamespace%3D%5C%2279307612-ae09-4fc0-81c3-e3f8b13a9927%5C%22%7D%20%7C%3D%20%60query%20trace%60%22,%22queryType%22:%22range%22,%22datasource%22:%7B%22type%22:%22loki%22,%22uid%22:%22loki%22%7D,%22editorMode%22:%22builder%22%7D%5D,%22range%22:%7B%22from%22:%221703500260000%22,%22to%22:%221703505119000%22%7D%7D%7D&schemaVersion=1&orgId=1

Expected Behavior

No response

Steps to Reproduce

see https://github.com/matrixorigin/MO-Cloud/issues/2132

Additional information

No response

[XuPeng-SH]

duplicate with #13216

[XuPeng-SH]

没有复现，继续跟踪

[XuPeng-SH]

assigned to @triump2020

[triump2020]

try to repro

[triump2020]

no repro

[triump2020]

本地tpcc 跑不出来，明天试试eks 环境, 一直跑.

[triump2020]

这里有两个疑问：1. 用户的事务 start ts >后台事务的 prepare ts , 为啥用户还是看到了 被后台事务删除的obj
2. 用户事务在很早之前就启动了，为啥过了很久才开始去读取obj? 这个时候obj 已经被gc 了.

[triump2020]

这里有两个疑问：1. 用户的事务 start ts >后台事务的 prepare ts , 为啥用户还是看到了 被后台事务删除的obj 2. 用户事务在很早之前就启动了，为啥过了很久才开始去读取obj? 这个时候obj 已经被gc 了.

用户事务的start ts >>后台事务的prepare ts(即事务的commit ts), 相差了5 个小时左右, 猜测5 个小时后后事务才启动？因为没有事务启动的日志信息， 如果假设成立，那就是问题1 导致的.

[triump2020]

加了日志之后，复现了一次:

e8711083-ac8e-11ee-87cb-525400777c3a 这个object 在2024/01/07 01:51:33 被partitionState.truncate 了 ; 但是过了接近40个小时之后，事务txn:9a2195ae5e434ce99f59a4b708e58b16/Active/S:1704707101101211126-1 在 2024/01/08 17:45:01 read 发现 file : e8711083-ac8e-11ee-87cb-525400777c3a 就不存在了.

[triump2020]

@aressu1985 fixed !

[aressu1985]

fixed