[CCR][FE Binlog] DROP admission depends on local config cache and diverges across frontends #67103

Problem

[CCR][FE Binlog] DROP admission depends on local config cache and diverges across frontends

Minimal reproduction path

Run a frontend cluster with table-level CCR Binlog enabled. Exercise DROP admission with a warm configuration cache, a cold cache, and after a leader change, then compare the dropped-table metadata and Binlog events on all frontends. Verify that the result is determined by persisted configuration, not local cache state.

Expected result

DROP admission and metadata Binlog output are identical across cache states and frontends.

Source

This report is a sanitized tracking record for Jira DORIS-28087. Internal hosts, paths, artifacts, build identifiers, and private logs are intentionally omitted.