From jira-return-11215-archive-asf-public=cust-asf.ponee.io@kafka.apache.org Tue Mar 27 19:31:05 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id AEE21180679 for ; Tue, 27 Mar 2018 19:31:04 +0200 (CEST) Received: (qmail 38568 invoked by uid 500); 27 Mar 2018 17:31:03 -0000 Mailing-List: contact jira-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@kafka.apache.org Delivered-To: mailing list jira@kafka.apache.org Received: (qmail 38551 invoked by uid 99); 27 Mar 2018 17:31:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Mar 2018 17:31:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 1619E1A03B9 for ; Tue, 27 Mar 2018 17:31:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.311 X-Spam-Level: X-Spam-Status: No, score=-99.311 tagged_above=-999 required=6.31 tests=[KAM_TIME=3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id Bv7WPQxTWRyk for ; Tue, 27 Mar 2018 17:31:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 05F805F36F for ; Tue, 27 Mar 2018 17:31:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id CB4F2E0E04 for ; Tue, 27 Mar 2018 17:31:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 330042150F for ; Tue, 27 Mar 2018 17:31:00 +0000 (UTC) Date: Tue, 27 Mar 2018 17:31:00 +0000 (UTC) From: "Guozhang Wang (JIRA)" To: jira@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (KAFKA-6718) Rack Aware Replica Task Assignment for Kafka Streams MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/KAFKA-6718?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-6718: ------------------------------------ Assignee: Deepak Goyal > Rack Aware Replica 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 > Affects Versions: 1.1.0 > Reporter: Deepak Goyal > Assignee: Deepak Goyal > Priority: Major > > |Machines in data centre are sometimes grouped in racks. Racks provide is= olation as each rack may be in a different physical location and has its ow= n power source. When=C2=A0tasks are properly replicated across racks, it pr= ovides fault=C2=A0tolerance in that if a rack goes down, the remaining rack= s can continue to serve traffic. > =C2=A0 > This feature is already implemented at Kafka [KIP-36|https://cwiki.apach= e.org/confluence/display/KAFKA/KIP-36+Rack+aware+replica+assignment]=C2=A0b= ut we needed similar for task assignments at Kafka Streams Application laye= r.=C2=A0 > =C2=A0 > This features enables replica tasks to be assigned on different racks fo= r fault-tolerance. > NUM_STANDBY_REPLICAS =3D x > totalTasks =3D 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-una= ware > # If (totalTasks >=3D 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, clust= er wide.| > We have added another config in StreamsConfig called "RACK_ID_CONFIG" whi= ch helps StickyPartitionAssignor to assign tasks in such a way that no two = replica tasks are on same rack if possible. > Post that=C2=A0it also helps=C2=A0to maintain stickyness with-in the rac= k.| -- This message was sent by Atlassian JIRA (v7.6.3#76005)