Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Change state to Accepted

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 [Change the link from KAFKA-1 to your own ticket]

JIRA:

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyKAFKA-19193

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

...

If the automatic partitioning is needed (i.e. no record partition or key is specified; or partitioner.ignore.keys is set to true):

  1. If the client rack is specified and there are partition leaders in the same rack, select the next partition from those “nearby” partitions. The current algorithm is followed in the other aspects, including load balancing.
  2. Select the next partition from all partitions following the current algorithm in the following cases:
    1. if the client rack is not specified;
    2. if there are no partitions with leaders in the same rack as the client;
    3. if all the “nearby” partitions are unavailable.
    4. if partitioner.rack.aware is false.

The new behavior will be controlled by configuration.

...

Key NameDescriptionValid ValuesDefault Value

partitioner.rack.aware

Controls whether the default partitioner is rack-aware. This has no effect when a custom partitioner is used.

true, falsefalse

client.rack

(already exists for consumers)

Specifies the rack of the client

strings

...