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
Please answer these questions before submitting your issue. Thanks!
The problem is in raftstore v1, after a table is truncated, the snapshot of the new table is not sent to TiFlash or not being handled.
However, in raftstore v2, the snapshot is handled by TiFlash, thus result in a empty segment.
Some intergrated tests like alter_truncated_table.test may fail.
The problem is snap.len in the following codes in raftstore v2 is always 3, even if the snapshot is actually empty.
PrehandleResult KVStore::preHandleSSTsToDTFiles(
RegionPtr new_region,
const SSTViewVec snaps,
uint64_t index,
uint64_t term,
DM::FileConvertJobType job_type,
TMTContext & tmt)
{
// if it's only a empty snapshot, we don't create the Storage object, but return directly.
if (snaps.len == 0)
{
return {};
}
As a consequence, the schea sync process in KVStore::preHandleSSTsToDTFiles will always be triggered, leading to InterpreterCreateQuery::createTable -> DatabaseTiFlash::createTable
Bug Report
Please answer these questions before submitting your issue. Thanks!
The problem is in raftstore v1, after a table is truncated, the snapshot of the new table is not sent to TiFlash or not being handled.
However, in raftstore v2, the snapshot is handled by TiFlash, thus result in a empty segment.
Some intergrated tests like alter_truncated_table.test may fail.
1. Minimal reproduce step (Required)
2. What did you expect to see? (Required)
3. What did you see instead (Required)
4. What is your TiFlash version? (Required)
The text was updated successfully, but these errors were encountered: