Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 0C55D200CD0 for ; Tue, 11 Jul 2017 00:59:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 0ACDB1648E2; Mon, 10 Jul 2017 22:59:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 585091648DB for ; Tue, 11 Jul 2017 00:59:04 +0200 (CEST) Received: (qmail 8616 invoked by uid 500); 10 Jul 2017 22:59:03 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 8603 invoked by uid 99); 10 Jul 2017 22:59:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Jul 2017 22:59:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 2C3FE194811 for ; Mon, 10 Jul 2017 22:59:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 6bUZ3Pu7M94S for ; Mon, 10 Jul 2017 22:59:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id D0357624BF for ; Mon, 10 Jul 2017 22:59:01 +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 53FBCE0D71 for ; Mon, 10 Jul 2017 22:59:01 +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 76017246A1 for ; Mon, 10 Jul 2017 22:59:00 +0000 (UTC) Date: Mon, 10 Jul 2017 22:59:00 +0000 (UTC) From: "Ambud Sharma (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-21234) Ambari rack awareness for Kafka MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 10 Jul 2017 22:59:05 -0000 [ https://issues.apache.org/jira/browse/AMBARI-21234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ambud Sharma updated AMBARI-21234: ---------------------------------- Attachment: AMBARI-21234-trunk.diff AMBARI-21234-2.5.diff > Ambari rack awareness for Kafka > ------------------------------- > > Key: AMBARI-21234 > URL: https://issues.apache.org/jira/browse/AMBARI-21234 > Project: Ambari > Issue Type: Improvement > Components: ambari-server > Reporter: Ambud Sharma > Assignee: Sebastian Toader > Fix For: 2.5.2 > > Attachments: AMBARI-21234-2.5.diff, AMBARI-21234-trunk.diff > > > As an operations person it would be nice to manage Kafka rack awareness via Ambari. Ambari allows node rack information to be configured and this information can then be pulled in the Kafka stack and populated in the server.properties file for Kafka. > Design: > This stack change uses the /clusterHostInfo/all_hosts and /clusterHostInfo/all_racks paths and materializes them to a variable. Then it uses linear search to find this node in the list of all hosts and it's corresponding rack id. This information is then stored in a variable called rack and which is materialized during the configure method of the broker scripts. > This stack change relies on the node rack information stored in Ambari therefore will enable both Ambari UI and Blueprints to be used for setting up Kafka broker rack information. -- This message was sent by Atlassian JIRA (v6.4.14#64029)