MINOR: Update and align broker/group config "importance" levels (KIP-848/107…

[suzhiking]

All the configs of KIP-848/1071/932 migrated from client side has importance level of MEDIUM. This PR updates and align config importance levels for new rebalance protocols for clients, streams, queues.

Client side has session.timeout.ms with importance level HIGH. Therefore following configs are set from MEDIUM to HIGH:

• group.streams.session.timeout.ms
• streams.session.timeout.ms
• group.consumer.session.timeout.ms
• consumer.session.timeout.ms
• group.share.session.timeout.ms
• share.session.timeout.ms

Client side has heartbeat.interval.ms with importance level HIGH. Therefore following configs are set from MEDIUM to HIGH:

• group.streams.heartbeat.interval.ms
• streams.heartbeat.interval.ms
• group.consumer.heartbeat.interval.ms
• consumer.heartbeat.interval.ms
• group.share.heartbeat.interval.ms
• share.heartbeat.interval.ms

For KIP-1071, client side has num.standby.replicas with importance level HIGH. Therefore following configs are set from MEDIUM to HIGH:

• group.streams.num.standby.replicas
• streams.num.standby.replicas

[mjsax]

Thanks for the PR.

One high level comment/question: for "classic" groups, there is only session.timeout.ms (which is a client side config). With the new KIPs, we get two configs, a broker config (which act as default for all groups if not overwritten), and the group config (that each group can set individually -- so this one, is "closer" to the previous client side config).

Thus, I am wondering if we should only bump the priority to HIGH for the group configs? But keep the broker one a medium?

[dajac]

Thanks for the PR.

Thus, I am wondering if we should only bump the priority to HIGH for the group configs? But keep the broker one a medium?

+1