Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents


Status

Current state"Under DiscussionAccepted"

Discussion thread: here [Change the link from the KIP proposal email archive to your own email thread]

JIRA: here

Released: 2.1.0

Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).

Motivation

Describe the problems you are trying to solveKIP-226 added support for dynamic update of  broker configuration.  In this KIP, we propose to extend the support to dynamic update of max.connections.per.ip/max.connections.per.ip.overrides configs. This will be useful  in the situations where a particular host (or set of hosts) is causing some trouble for the brokers.  Administrators can dynamically update these configs to restrict the connections coming from faulty hosts (or)  enable connections only from allowed hosts.

Proposed Changes

Use case: To restrict the connections coming from faulty clients/hosts  (or) to configure IP-based filtering of incoming connections (max.connections.per.ip  = 0 and valid max.connections.per.ip.overrides config value)

Config scope: Default for whole cluster (/configs/brokers/<default>)

Config options:

max.connections.per.ip
max.connections.per.ip.overrides

Dynamic update changes:

SocketServer ConnectionQuotas will be updated with the new values. Existing connections will not be affected, restrictions will be applied on
new connection creationsDescribe the new thing you want to do in appropriate detail. This may be fairly extensive and have large subsections of its own. Or it may be a few sentences. Use judgement based on the scope of the change.

Compatibility, Deprecation, and Migration Plan

  • What impact (if any) will there be There won't be any impact on existing users?
  • If we are changing behavior how will we phase out the older behavior?
  • If we need special migration tools, describe them here.
  • .
  • There won't be any change of current behavior.
  • No migration tool requiredWhen will we remove the existing behavior?

Rejected Alternatives