KIP-835: metadata.max.idle.interval.ms shoud be much bigger than broker.heartbeat.interval.ms (#12238)
KIP-835: metadata.max.idle.interval.ms shoud be much bigger than broker.heartbeat.interval.ms (#12238)

The active quorum controller will append NoOpRecord periodically to increase metadata LEO, however, when a broker startup, we will wait until its metadata LEO catches up with the controller LEO, we generate NoOpRecord every 500ms and send heartbeat request every 2000ms.

It's almost impossible for a broker to catch up with the controller LEO if the broker sends a query request every 2000ms but the controller LEO increases every 500ms, so the tests in KRaftClusterTest will fail.

Reviewers: José Armando García Sancio <a8f36d709c55b131453e2fdebab89d11b4e5c5e0@users.noreply.github.com>, showuon <43372967+showuon@users.noreply.github.com>, Colin Patrick McCabe <cmccabe@confluent.io>
apache/kafka,lindong28/kafka,lindong28/kafka,lindong28/kafka,guozhangwang/kafka,guozhangwang/kafka,apache/kafka,lindong28/kafka,guozhangwang/kafka,apache/kafka,apache/kafka,guozhangwang/kafka