[KAFKA-6718] Rack Aware Stand-by Task Assignment for Kafka Streams

• Type: New Feature
• Status: In Progress
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 3.2.0
• Component/s: streams
• Labels: kip
• Assignee: Levani Kokhreidze
• Reporter: Deepak Goyal
• Reviewer: Ashish Surana
• Created: 27/Mar/18 13:02
• Updated: 6 days ago 14:10

Description

Machines in data centre are sometimes grouped in racks. Racks provide isolation as each rack may be in a different physical location and has its own power source. When tasks are properly replicated across racks, it provides fault tolerance in that if a rack goes down, the remaining racks can continue to serve traffic.   This feature is already implemented at Kafka KIP-36 but we needed similar for task assignments at Kafka Streams Application layer.    This features enables replica tasks to be assigned on different racks for fault-tolerance. NUM_STANDBY_REPLICAS = x totalTasks = x+1 (replica + active) If there are no rackID provided: Cluster will behave rack-unaware If same rackId is given to all the nodes: Cluster will behave rack-unaware If (totalTasks <= number of racks), then Cluster will be rack aware i.e. each replica task is each assigned to a different rack. Id (totalTasks > number of racks), then it will first assign tasks on different racks, further tasks will be assigned to least loaded node, cluster wide.

We have added another config in StreamsConfig called "RACK_ID_CONFIG" which helps StickyPartitionAssignor to assign tasks in such a way that no two replica tasks are on same rack if possible.
Post that it also helps to maintain stickyness with-in the rack.|

Issue Links

• duplicates: KAFKA-6642 Rack aware task assignment in kafka streams
• is related to: KAFKA-10686 Pluggable standby tasks assignor for Kafka Streams
• links to: GitHub Pull Request #4785
• links to: GitHub Pull Request #10785
• links to: GitHub Pull Request #10802
• links to: GitHub Pull Request #10851
• mentioned in: Page Loading...