glorv

There are three kinds of event, that can cause `EpochNotMatch` errors: - region leader changes. This will cause increase of region conf version. After #408 related schedulers will be disabled...

Since the `epoch not match` errors are due to concurrently split regions in the same range, here is the config to reproduce this issue: - Source data contains randomly generated...

We have optimized the stability of lightning local backend in the past few months: - #408. Disable pd region scheduler and region merge to decrease the possibility that lightning ingest...

Since this is a non-fatal error and a expected behavior, so I think it will be ok to change the error level to `WARN` to make it less confusing? @kennytm

@nolouch PTAL. https://github.com/tikv/tikv/blob/84466febe406809aab936197ec897b6adac36d70/components/pd_client/src/util.rs#L315 since this is a non-fatal error (because it is in a retry loop), it's better to change this log for `ERROR` level to `WARN` level to make...

@okJiang PTAL. Seems we still try to parse some DDLs that tidb doesn't support.

> with an all schema pattern, the event was skipped correctly. > > ``` > filters: > filter-rule-1: > schema-pattern: "*" > events: [".*\\s+DROP\\s+PROCEDURE"] > action: Ignore > ``` So...

@DanielZhangQD @KanShiori @nolouch PTAL

@azurezyq Could you please take a look?

@overvenus who is responsible for this issue now?