INFO Scheduled shutdown for WorkerConnector [DBZ-4212]

Migrated from [DBZ-4212](https://issues.redhat.com/browse/DBZ-4212)

Hello team.

I wanted to ask you in regards of a estrange behavior that Confluent-kafka is presenting since the upgrade to 6.1. 

We have been noticing that all the connectors are being restarted, apparently, every hour or so. Is this a new feature that gets automatically implemented? Is there a way to stop this restart from happening?

On the other hand, we are having issues resolving an error on the connectors. It is failing with issues recovering the database history. It recommends you to increase the value of the variable database.history.kafka.recovery.poll.interval.ms. We have already done that from 100 ms to 172800000 ms and it keeps happening. What could be provoking this issues? What should be done to resolve this?

Kind regards.

Start with the WorkerConnector behavior described after the upgrade to 6.1, then inspect connector restart timing and the database-history recovery error in the available logs and configuration. Compare the configured database.history.kafka.recovery.poll.interval.ms value with the observed failures; done means identifying the cause of both behaviors and documenting a confirmed resolution.

Written by the indexing model from the issue text.