Return-Path: X-Original-To: apmail-kafka-dev-archive@www.apache.org Delivered-To: apmail-kafka-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1E2B31058D for ; Mon, 8 Dec 2014 15:15:13 +0000 (UTC) Received: (qmail 51517 invoked by uid 500); 8 Dec 2014 15:15:12 -0000 Delivered-To: apmail-kafka-dev-archive@kafka.apache.org Received: (qmail 51458 invoked by uid 500); 8 Dec 2014 15:15:12 -0000 Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@kafka.apache.org Delivered-To: mailing list dev@kafka.apache.org Received: (qmail 51446 invoked by uid 99); 8 Dec 2014 15:15:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Dec 2014 15:15:12 +0000 Date: Mon, 8 Dec 2014 15:15:12 +0000 (UTC) From: "Andrii Biletskyi (JIRA)" To: dev@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (KAFKA-1802) Add a new type of request for the discovery of the controller MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/KAFKA-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14237954#comment-14237954 ] Andrii Biletskyi commented on KAFKA-1802: ----------------------------------------- Patch is available under parent ticket - KAFKA-1694 > Add a new type of request for the discovery of the controller > ------------------------------------------------------------- > > Key: KAFKA-1802 > URL: https://issues.apache.org/jira/browse/KAFKA-1802 > Project: Kafka > Issue Type: Sub-task > Reporter: Joe Stein > Assignee: Andrii Biletskyi > Fix For: 0.8.3 > > > The goal here is like meta data discovery is for producer so CLI can find which broker it should send the rest of its admin requests too. Any broker can respond to this specific AdminMeta RQ/RP but only the controller broker should be responding to Admin message otherwise that broker should respond to any admin message with the response for what the controller is. -- This message was sent by Atlassian JIRA (v6.3.4#6332)