[
https://issues.apache.org/jira/browse/KAFKA-6718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16986715#comment-16986715
]
Levani Kokhreidze edited comment on KAFKA-6718 at 12/3/19 8:36 AM:
-------------------------------------------------------------------
Hi [~vvcephei]
Would appreciate your thoughts on this ticket if there is anything specific you
think we must take into account while implementing this new feature.
KIP-441 has a lot of work with standby tasks, wondering if we should unify this
in the KIP-441 (pretty sure we shouldn't, thinking out loud), should we wait
for KIP-441, or they can be done in parallel?
was (Author: lkokhreidze):
Hi [~vvcephei]
Would appreciate your thoughts on this ticket if there're anything specific you
think we must take into account while implementing this new feature.
KIP-441 has a lot of work with standby tasks, wondering if we should unify this
in the KIP-441 (pretty sure we shouldn't, thinking out loud), should we wait
for KIP-441, or they can be done in parallel?
> Rack Aware Stand-by Task Assignment for Kafka Streams
> -----------------------------------------------------
>
> Key: KAFKA-6718
> URL: https://issues.apache.org/jira/browse/KAFKA-6718
> Project: Kafka
> Issue Type: New Feature
> Components: streams
> Reporter: Deepak Goyal
> Priority: Major
> Labels: needs-kip
>
> |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|https://cwiki.apache.org/confluence/display/KAFKA/KIP-36+Rack+aware+replica+assignment]
> 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.|
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
