You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From the log, we can see that Titan GC has already selected the blob file 256 as a candidate. Whereas the DeleteFilesInRange deletes the blob file 256 directly. So when the GC is finished and to delete blob file 256, it may find blob file 256 is already deleted and panic.
Influence:
make tikv panic, but doesn't affect data correctness. After a restart(need to delete panic_mark manually), everything will work well.
The text was updated successfully, but these errors were encountered:
tikv panic due to titan deletes a already deleted blob
Titan log:
From the log, we can see that Titan GC has already selected the blob file 256 as a candidate. Whereas the
DeleteFilesInRange
deletes the blob file 256 directly. So when the GC is finished and to delete blob file 256, it may find blob file 256 is already deleted and panic.Influence:
make tikv panic, but doesn't affect data correctness. After a restart(need to delete panic_mark manually), everything will work well.
The text was updated successfully, but these errors were encountered: