sorter iterator can utilize too much CPU if there are lots of DeleteRange records #11065
Labels
area/ticdc
Issues or PRs related to TiCDC.
severity/moderate
This is a moderate bug.
type/bug
This is a bug.
Projects
Comments
hicqu
added
affects-7.5
affects-8.0
affects-8.1
severity/moderate
|
Duplicate with #11078, closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What did you do?
Start a TiCDC changefeed to replicate 4K tables. And there are a lot exists data.
What did you expect to see?
No response
What did you see instead?
Sorter iterators can utilize too much CPU if there are lots of DeleteRange records:
Versions of the cluster
Upstream TiDB cluster version (execute
SELECT tidb_version();in a MySQL client):(paste TiDB cluster version here)Upstream TiKV version (execute
tikv-server --version):(paste TiKV version here)TiCDC version (execute
cdc version):(paste TiCDC version here)The text was updated successfully, but these errors were encountered: