PK table messagesIn/bytesIn metrics double-counted due to CDC log

[swuferhong]

Search before asking

• I searched in the issues and found nothing similar.

Motivation

For primary key tables, every write to putToLocalKv increments the table-level and server-level messagesInPerSecond and bytesInPerSecond metrics twice: once for the KV store write, and once for the internal CDC log append.

This causes the reported throughput to be roughly 2x the actual write volume, which is confusing for users monitoring PK table performance — the metric no longer reflects the number of records the user actually wrote.

The CDC log is an internal implementation detail of PK tables (used for changelog replication). Its I/O should not be aggregated into the user-facing table-level metrics, as users have no awareness of or control over it.

Solution

No response

Anything else?

No response

Willingness to contribute

• I'm willing to submit a PR!