In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

Bug report

For bug reports, provide this information, please:

see that

https://debezium.zulipchat.com/#narrow/stream/348104-community-mysql/topic/Estimated.20row.20count.20too.20long.20to.20complete/near/426318539

What Debezium connector do you use and what version?

2.4.1

What is the connector configuration?

```

{{ "database.server.id": "300000","topic.prefix": "prod-aurora-phemex-t-order-history","transforms.Reroute.table.sync.config.instance": "prod-aurora-phemex-t-order-history","schema.history.internal.kafka.topic": "schema-changes.prod-aurora-phemex-t-order-history","transforms.Reroute.table.sync.config.kafka.topic": "prod-aurora-phemex-t-order-history-table-sync-config","signal.kafka.topic": "prod-aurora-phemex-t-order-history-signal","notification.sink.topic.name": "prod-aurora-phemex-t-order-history-notification","signals.consumer.group.id": "prod-aurora-phemex-t-order-history-signal-consumer","signal.enabled.channels": "kafka","snapshot.max.threads": "5","database.include.list": "phemex","table.include.list": "phemex.t_order_.*","connector.class": "io.debezium.connector.mysql.MySqlConnector","connector.displayName": "MySQL","connector.id": "mysql","decimal.handling.mode": "string","include.schema.changes": "false","schema.history.internal.kafka.bootstrap.servers": "2","schema.history.internal.store.only.captured.tables.ddl": "true","snapshot.locking.mode": "none","snapshot.mode": "schema_only","tombstones.on.delete": "false","topic.creation.default.partitions": "1","topic.creation.default.replication.factor": "3","signal.kafka.bootstrap.servers": " ","signals.consumer.auto.offset.reset": "latest","signals.consumer.enable.auto.commit": "true","read.only": "true"}}

```

What is the captured database version and mode of depoyment?

(E.g. on-premises, with a specific cloud provider, etc.)

<Your answer>

mysql 5.7

kafka-connect mode

What behaviour do you expect?

speed up the estimate process

What behaviour do you see?

<Your answer>

Do you see the same behaviour using the latest relesead Debezium version?

(Ideally, also verify with latest Alpha/Beta/CR version)

<Your answer>

Do you have the connector logs, ideally from start till finish?

(You might be asked later to provide DEBUG/TRACE level log)

<Your answer>

How to reproduce the issue using our tutorial deployment?

<Your answer>

Feature request or enhancement

For feature requests or enhancements, provide this information, please:

Which use case/requirement will be addressed by the proposed feature?

speed up the estimate when table size is too many eg.(90000+).

Implementation ideas (optional)

using multiple threads estimate or disable estimate