Skip to content

eventservice: integrity behavior depends on the first registered changefeed #6334

Description

@lidezhu

What did you do?

integrity-check-level is a changefeed-level configuration, but EventService creates one shared mounter per upstream cluster using the first registered dispatcher’s integrity config:

mounter: event.NewMounter(tz, integrity)

All later changefeeds on the same cluster reuse this mounter.

What did you expect to see?

Each changefeed should use its own integrity configuration.

What did you see instead?

As described above.

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)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

affects-26.9This bug affects the TiDB X 26.9.x versions.affects-8.5This bug affects the 8.5.x(LTS) versions.severity/moderatetype/bugThe issue is confirmed as a bug.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions