Jay
> `committer-concurrency` is configurable and its default value is not 1024 I don't think this configuration matters. It's possible to increase the transaction count while decrease this configuration to achieve...
So have you tried to use it in TiKV? Is everything working well?
+1 surprised and lol
How about running the test without dropping tables?
Note delete files in range is only invoked when all existing snapshots are younger than the delete range command is generated. So I think conf change should not break correctness.
I checked the logs, there is no "delete data in range" during the time when hash is being computed. @Lily2025 can you reproduce the issue with compaction filter gc disabled?
Any progress on the issue?
Does it need to be solved? Or is it an improvement?
Perhaps we should keep latest commit informations and apply informations when destroying a peer and include them in response.
Remove triage related tags for now.