Ping Yu

/rebuild

@haojinming @zeminzhou PTAL~

I think yes. Which parameters, and why they affect the latency in your case ?

> This parameter in TiKV can cause a timestamp discrepancy with physical time, resulting in incorrect calculations, but seems no real negative effect. This parameter is configurable, See https://docs.pingcap.com/tidb/v6.5/tikv-configuration-file#alloc-ahead-buffer-new-in-v640. It's...

> Great! Thank you master @pingyu But I think hard code parameters in `https://github.com/tikv/migration/blob/main/cdc/cdc/sink/tikv.go` is still an issue. Perhaps we could consolidate these parameters into a single file as constant...

> > > Great! Thank you master @pingyu But I think hard code parameters in `https://github.com/tikv/migration/blob/main/cdc/cdc/sink/tikv.go` is still an issue. Perhaps we could consolidate these parameters into a single file...

Reopen because another fail case is met. https://github.com/tikv/migration/runs/7559704549?check_suite_focus=true ``` === Failed === FAIL: cdc/kv Test (unknown) Error: 7/28 12:22:27.405 +00:00] [ERROR] [client.go:1041] ["tikv reported the request cluster ID mismatch error,...

Another case https://github.com/tikv/migration/runs/7628273817?check_suite_focus=true ``` === Failed === FAIL: cdc/kv Test (unknown) Error: 8/02 09:18:33.779 +00:00] [ERROR] [client.go:1041] ["tikv reported the request cluster ID mismatch error, which is not expected"] [tikvCurrentClusterID=0]...

Another case: https://github.com/tikv/migration/runs/8010626295?check_suite_focus=true ``` === Failed === FAIL: cdc/kv Test (292.92s) Error: 8/25 07:27:59.222 +00:00] [ERROR] [client.go:1041] ["tikv reported the request cluster ID mismatch error, which is not expected"] [tikvCurrentClusterID=0]...

You can send a feature request and describe what you want in detail. See the hints in template.