CDC should not send changes of un-captured key ranges #10073
Labels
component/CDC
Component: Change Data Capture
difficulty/easy
Difficulty: Easy. Ideal for beginners.
severity/minor
type/bug
Type: Issue - Confirmed a bug
Projects
Bug Report
CDC sends changes of un-captured key ranges. It has overheads for both TiCDC and TiKV, especially for TiKV when a changefeed enables old value. For example, when we start to load data by INSERT SQL, TiKV caches old value by region, so it may cache both row data and index data (which is not unnecessary to captured). In pessimistic txn, TiKV may not cache all indexes, it may lead to old value cache miss.
In the red box, the cache hit rate should be 100%.
This issue is found during the development of #10072
What version of TiKV are you using?
TiKV 5.0.0
Steps to reproduce
What did you expect?
100% cache hit.
What did happened?
90% cache hit.
The text was updated successfully, but these errors were encountered: