What did you do?
When event store iterator creation or first read fails, the scanner usually only sees a nil iterator and stops scanning. However, the real underlying error is not reported, which makes failures hard to diagnose and can hide the actual root cause.
What did you expect to see?
No response
What did you see instead?
Event store iterator errors should be propagated to eventScanner and returned/logged by the scan path, so the caller can see the real reason for the scan failure
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)
What did you do?
When event store iterator creation or first read fails, the scanner usually only sees a nil iterator and stops scanning. However, the real underlying error is not reported, which makes failures hard to diagnose and can hide the actual root cause.
What did you expect to see?
No response
What did you see instead?
Event store iterator errors should be propagated to
eventScannerand returned/logged by the scan path, so the caller can see the real reason for the scan failureVersions 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)